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?
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.
Since max-age=0 requests can't be fulfilled without revalidating the
object they don't benefit from this header rewrite, and requests with
max-age!=0 that can benefit from the header rewrite won't be affected
by this change.
Am I making sense? Have I missed something fundamental?
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [EMAIL PROTECTED]
---------------------------------------------------------------------------
"...and then you howled with rage." - Alexander
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
