Comments on: mod_expires and Cache Killers http://blog.cherouvim.com/mod_expires-and-cache-killers/ software engineering for beginners Mon, 23 Jan 2012 06:17:54 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: High Performance Web Sites :: Even Faster Web Sites in Skiathos http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1194 High Performance Web Sites :: Even Faster Web Sites in Skiathos Thu, 10 Sep 2009 06:10:37 +0000 http://blog.cherouvim.com/?p=113#comment-1194 [...] Ioannis Cherouvim, a software engineer from Greece, sent me this photo: [...] [...] Ioannis Cherouvim, a software engineer from Greece, sent me this photo: [...]

]]> By: javier http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1117 javier Wed, 13 May 2009 10:42:25 +0000 http://blog.cherouvim.com/?p=113#comment-1117 The solution is not complete. In one of our J2EE products we are using the tuckey url rewriter to rewrite urls with the following: /path/path/resource-.ext the rule we use is the following. ^([^ ]+)-([0-9]+)\.([a-z]+)$ $1.$3 The filter only applies to paths under /resources/ so only applies to css, js, etc This is not enough because inside the css files you point to images as well. The same problem could happen in the js files. In order to sort these issue out we use a filter that modifies these kind of resources on the flight and caches them. Our system finally publishes a jmx bean that allows us to change the version. By default the version is system.currentTimeMillis() that changes everytime we restart the server. The solution is not complete. In one of our J2EE products we are using the tuckey url rewriter to rewrite urls with the following:

/path/path/resource-.ext

the rule we use is the following.

^([^ ]+)-([0-9]+)\.([a-z]+)$
$1.$3

The filter only applies to paths under /resources/ so only applies to css, js, etc

This is not enough because inside the css files you point to images as well. The same problem could happen in the js files.

In order to sort these issue out we use a filter that modifies these kind of resources on the flight and caches them.

Our system finally publishes a jmx bean that allows us to change the version. By default the version is system.currentTimeMillis() that changes everytime we restart the server.

]]> By: Ochoto http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1116 Ochoto Wed, 13 May 2009 07:24:48 +0000 http://blog.cherouvim.com/?p=113#comment-1116 Squid's default configuration is not to cache urls with a query string. Squid’s default configuration is not to cache urls with a query string.

]]> By: Yann Cébron http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1115 Yann Cébron Wed, 13 May 2009 06:50:00 +0000 http://blog.cherouvim.com/?p=113#comment-1115 JEE solution http://packtag.sf.net - works very well for me (unfortunately it does not support rewriting URLs for anything else than CSS/JS - yet) JEE solution http://packtag.sf.net – works very well for me (unfortunately it does not support rewriting URLs for anything else than CSS/JS – yet)

]]> By: Jordi Hernandez http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1114 Jordi Hernandez Tue, 12 May 2009 15:43:40 +0000 http://blog.cherouvim.com/?p=113#comment-1114 I think the request string issue mentioned by Simon happened in older browsers indeed, but nowadays it is more or less safe to use this technique. The HTTP spec does indeed mandate browsers to use cache for such requests. And now the plug: java web apps can benefit from this technique and many others to accomplish nearly all of the YUI blog recommendations by using Jawr (https://jawr.dev.java.net). Images are still not supported but javascript and CSS are indeed combined,minified, gzipped and assigned a version-dependant URL (actually without request params). Jawr also has a debug mode in which files are served uncompressed and with a per-request changing param which forces the browser to reload and helps code-deply-test cycles. I think the request string issue mentioned by Simon happened in older browsers indeed, but nowadays it is more or less safe to use this technique. The HTTP spec does indeed mandate browsers to use cache for such requests.
And now the plug: java web apps can benefit from this technique and many others to accomplish nearly all of the YUI blog recommendations by using Jawr (https://jawr.dev.java.net). Images are still not supported but javascript and CSS are indeed combined,minified, gzipped and assigned a version-dependant URL (actually without request params). Jawr also has a debug mode in which files are served uncompressed and with a per-request changing param which forces the browser to reload and helps code-deply-test cycles.

]]> By: cherouvim http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1109 cherouvim Sun, 03 May 2009 20:27:53 +0000 http://blog.cherouvim.com/?p=113#comment-1109 Thanks for your input Simon, I'll have to do some more research. On the other hand it's a bit hard to think that slashdot would have gotten that wrong. Thanks for your input Simon, I’ll have to do some more research. On the other hand it’s a bit hard to think that slashdot would have gotten that wrong.

]]> By: Simon Willison http://blog.cherouvim.com/mod_expires-and-cache-killers/comment-page-1/#comment-1108 Simon Willison Sun, 03 May 2009 20:19:44 +0000 http://blog.cherouvim.com/?p=113#comment-1108 I believe using a version number in a query string can cause some browsers and/or proxies to avoid caching an asset at all - it's safer to bake the version number in to the filename or directory path in some way. I believe using a version number in a query string can cause some browsers and/or proxies to avoid caching an asset at all – it’s safer to bake the version number in to the filename or directory path in some way.

]]>