On May 21, 2007, at 7:49 AM, Niklas Edmundsson wrote:
Does anybody see a problem with changing mod_cache to not update the stored headers when the request has max-age=0, the body turns out not to be stale and the on-disk header hasn't expired?
Yes, the problem is that it will break content management systems that need to refresh a cache front-end after the content has changed.
The rationale behind this is that there are hordes of stupid "download managers" that always issue this kind of request, and multiple in parallell to the same file at that. This hammers the entire cache-layer by causing headers to be rewritten for each request.
Why don't you just add an ignore of cache-control on requests from those stupid download managers? A simple BrowserMatch should do. ....Roy
