<div dir="ltr"><div><div><div><div><div><div>Hi Paul,<br><br></div>This is possible for example with the link tag.<br></div>If you add URL query parameters, e.g. the datelastmodified of the linked file, OpenCms will generate exported versions with a fingerprint:<br>
</div><cms:link>/.../my.css?t=${datelastmodified}</cms:link><br></div>Of course you first have to read the datelastmodified and put it into page context.<br></div>And the CSS file must have set the export property to true, either directly or inherited.<br>
<br></div>Kind regards,<br>Stephan<br><br><div><div><div><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-11 16:23 GMT+02:00 Paul-Inge Flakstad <span dir="ltr"><<a href="mailto:flakstad@npolar.no" target="_blank">flakstad@npolar.no</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="NO-BOK"><div><p class="MsoNormal"><span lang="EN-US">Hi,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">Has anyone considered URL fingerprinting in OpenCms?<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I’m Curious because I’m thinking about modifying the export/link handler (?) to manage this. Since it’s already doing some modification to the URLs, it should be possible to extend that some more – right ..?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">What I have in mind is adding the fingerprint when exporting (similarly to how /opencms/export/ is injected). <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">E.g. if the VFS resource’s offline URL is<u></u><u></u></span></p><p class="MsoNormal" style="text-indent:35.4pt"><span lang="EN-US">/static/my.css <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">the online URL would become<u></u><u></u></span></p><p class="MsoNormal" style="text-indent:35.4pt"><span lang="EN-US">/opencms/export/static/my-32819023810832091.css<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">when requested online.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">Same for images, javascript and whatnot.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">With fingerprinting in place, one could set the appropriate headers in Apache (or whatever’s in front) and ta-daaaa pages would load (possibly a lot) faster, because many resources would be cached client-side.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">Would sure like to hear your thoughts on this, if you have any.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">(Don’t know about URL fingerprinting? Then you should read this: <a href="https://developers.google.com/speed/docs/insights/LeverageBrowserCaching" target="_blank">https://developers.google.com/speed/docs/insights/LeverageBrowserCaching</a>)<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">Cheers,<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US">Paul<u></u><u></u></span></p></div></div><br>
_______________________________________________<br>
This mail is sent to you from the opencms-dev mailing list<br>
To change your list options, or to unsubscribe from the list, please visit<br>
<a href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev" target="_blank">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a><br>
<br>
<br>
<br>
<br></blockquote></div><br></div>