On Thu, Aug 27, 2009 at 2:07 AM, Thomas Balthazar<[email protected]> wrote: > Hello Ryan, > > Thanks a lot for your in-depth explanation. > > If I understand you correctly, if I specify : > response.headers['Cache-Control'] = "public, must-revalidate" > or > expires_in 0, :public => true > > then the backend will be asked if the content is still fresh for every > request, but the backend will only generate a new response if the etag > has changed (if the etag hasn't changed, a 304 not-modified header > will be sent and the content will be served from the cache, as in the > last drawing in your article : > http://tomayko.com/writings/things-caches-do ) > > I tried both solutions, and here are my results : > > * expires_in 0 : > - with Safari, the page doesn't seem to be served from the cache > - with Firefox, the page is served from the cache and correctly > expired when I create a new item, it is working as expected > > * response.headers['Cache-Control'] = "must-revalidate" > - with Safari and Firefox : the page is cached but not expired when I > create a new item > > Again, a 15.2Mb screencast that shows it in details : > http://dl.getdropbox.com/u/40466/tmp/heroku-caching-2.mov
Interesting. I'll dig in and take a look at this today. Thanks, Ryan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
