On Tuesday, October 2, 2012 9:50:39 PM UTC+1, jcoleman wrote: > > How does Rails generate ETags by default? I've got config. > action_controller.perform_caching set to true in production so that I can > use page-level caching in a few specific places, but it seems that Rails is > automatically setting ETags on *all* responses even though I'm not using > fresh_when or the stale? helpers in any of my actions. How is Rails > deciding to do this and how do I disable it without killing page caching? >
The Rack::Etag middleware does this, using an MD5 of the response body as the actual etag. I would have thought that removing Rack::ETag from the middleware stack would hobble this. Fred -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/wkhYqV2j6DAJ. For more options, visit https://groups.google.com/groups/opt_out.
