http://blog.futtta.be/2007/04/06/cache-header-magic-or-how-i-learned-to-love-http-response-headers/ Frank Goossens' Twitterless twaddle Tue, 07 Feb 2012 18:48:55 +0000 hourly 1 http://wordpress.org/?v= http://blog.futtta.be/2007/04/06/cache-header-magic-or-how-i-learned-to-love-http-response-headers/#comment-25 futtta Mon, 09 Apr 2007 16:16:47 +0000 http://newblog.futtta.be/index.php/2007/04/06/cache-header-magic-or-how-i-learned-to-love-http-response-headers/#comment-25 There is, off course, more to be found when delving into documentation about cache-control. One of the things I learned last Friday was that 'cache-control:must-revalidate' does not imply that an object has to be revalidated at every hit, but that it has to be revalidated when expired. Turns out that http/1.1 foresees situations where the origin server is unreachable. Without the aforementioned directive the caching-layer is allowed to return the object although expired, whilst with these headers it will have to return an error. There is, off course, more to be found when delving into documentation about cache-control. One of the things I learned last Friday was that ‘cache-control:must-revalidate’ does not imply that an object has to be revalidated at every hit, but that it has to be revalidated when expired. Turns out that http/1.1 foresees situations where the origin server is unreachable. Without the aforementioned directive the caching-layer is allowed to return the object although expired, whilst with these headers it will have to return an error.

]]>