It seems to me (though I'm not positive?) that caches_page is overwritten to simply write "response.headers['Cache-Control'] = 'public, max-age=300'", as evidenced by the git post-push action detecting and installed caches_page_via_http.
Does anyone know if this is indeed the case? If so, I wonder why http://docs.heroku.com/http-caching doesn't explain as much and recommend using caches_page rather than explicitly writing cache-control headers? Seems like a more elegant approach? Also - cache key name space is the full URL (including the query string), for either approach, right? If so, which I assume is the case, I saw definite weirdness yesterday where: a) Cached content for /controller/id?foo=bar was being return for / controller/id (i.e. no query string). b) Shift-reloading, restarting, even repushing the app was still serving the same cached content (it had a session specific flash) Continued for a good two hours (10 - 12 EST)...and now I can't repro it. I know it was Halloween and all...but I swear I was not making things up. Anyone ever seen this kind of behavior? -- 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.
