I've recently been made aware that Apache supports something called
"end-to-end reload" (apparently documented in http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.4)
.
I'm curious if Squid exhibits similar behavior.
The way the Apache developers appear to interpret this spec, a
*request* containing a "Cache-Control: no-cache" header will
essentially "purge" the Apache's cache during a forced reload request
to the backend. Previously I had assumed that a client-initiated
forced reload would just bypass any proxy caches without touching the
cached entries themselves, except for the client's cache. Is this not
the way Squid behaves?
Ric
Received on Wed Aug 05 2009 - 14:59:08 MDT
This archive was generated by hypermail 2.2.0 : Wed Aug 05 2009 - 12:00:03 MDT