Markus Meyer wrote:
Amos Jeffries schrieb:
Force a refresh (using wget, squidclient, or your browser) or set
http://www.squid-cache.org/Doc/config/negative_ttl/ to a sufficiently
low value and reload.
The recommended value being zero.
Ok, with this the Squid would not memorize the 404s. But how can I
prevent it from invalidating cached content in case it's parents go down?
This is just a kind of rescue plan in case our backend servers have a
disaster. It happend to me twice now and I want to make sure that the
proxies are still delivering their content for the short period we need
to get the backend servers running again.
404s can have Cache-Control: and Expires: headers like any other
response. The we server should be able to more accurately set a duration
of 404 than Squid can.
All the negative_ttl does is set a minimum caching time for 4xx and 5xx
issues. Any explicit Expiry info longer than that is expected to be
treated according to RFC and cached.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
Current Beta Squid 3.1.0.8
