Comments on: Rack cache headers http://nutrun.com/weblog/rack-cache-headers/ nutrun Fri, 08 Jan 2010 06:54:37 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: nutrun » Blog Archive » Rack::CacheHeaders code http://nutrun.com/weblog/rack-cache-headers/comment-page-1/#comment-1494 nutrun » Blog Archive » Rack::CacheHeaders code Mon, 18 May 2009 13:22:37 +0000 http://nutrun.com/?p=204#comment-1494 [...] few months ago I wrote about a possible method for centrally configuring HTTP cache headers in Rack based web applications [...] [...] few months ago I wrote about a possible method for centrally configuring HTTP cache headers in Rack based web applications [...]

]]> By: Ryan Tomayko http://nutrun.com/weblog/rack-cache-headers/comment-page-1/#comment-1242 Ryan Tomayko Sat, 08 Nov 2008 17:39:15 +0000 http://nutrun.com/?p=204#comment-1242 Nice. There's a <a href="http://tomayko.com/src/rack-cache/configuration" rel="nofollow">configuration system</a> in Rack::Cache and specifying cache policy was one of the things I had envisioned it being used for, but this looks really simple and elegant. Also, regarding Justin's comment - I've noticed that a lot of people seem to have the impression that Rack::Cache was designed to automatically set the ETag, Last-Modified, Cache-Control, and Expires headers for an full-blown caching server upstream. In reality, Rack::Cache <em>is</em> a full blown cache. It uses the headers set by your app to implement the caching semantics defined in RFC 2616. It actually implements more of the spec than Varnish. Clearly, I have some work to do in order to convey all this. Nice. There’s a configuration system in Rack::Cache and specifying cache policy was one of the things I had envisioned it being used for, but this looks really simple and elegant.

Also, regarding Justin’s comment – I’ve noticed that a lot of people seem to have the impression that Rack::Cache was designed to automatically set the ETag, Last-Modified, Cache-Control, and Expires headers for an full-blown caching server upstream. In reality, Rack::Cache is a full blown cache. It uses the headers set by your app to implement the caching semantics defined in RFC 2616. It actually implements more of the spec than Varnish.

Clearly, I have some work to do in order to convey all this.

]]> By: George Malamidis http://nutrun.com/weblog/rack-cache-headers/comment-page-1/#comment-1240 George Malamidis Sat, 08 Nov 2008 12:34:16 +0000 http://nutrun.com/?p=204#comment-1240 Hi Justin,I might be missing something, but as far as I understand it, Rack::Cache deals with cache storage based on an application's response cache headers. This is a means for configuring those headers per URI path. Hi Justin,I might be missing something, but as far as I understand it, Rack::Cache deals with cache storage based on an application’s response cache headers. This is a means for configuring those headers per URI path.

]]> By: Justin http://nutrun.com/weblog/rack-cache-headers/comment-page-1/#comment-1238 Justin Sat, 08 Nov 2008 04:26:53 +0000 http://nutrun.com/?p=204#comment-1238 How is this any different then Rack::Cache? How is this any different then Rack::Cache?

]]>