[squid-users] negative ttl and 404

2009-10-08 Thread Frank Ruiz
Is there a way to force a minimum age on 404 errors? We have a
situation where it appears 404s are getting cached, and squid is
honoring the TTLs of the webserver (could be hours/days). So the 404s
persist after the default negative ttl of 5 minutes.

Can we force this to 5 minutes regardless of the TTL that is passed by
the webserver?

Maybe an acl/refresh pattern or something? Didn't see anything for 404s.

Thanks!


[squid-users] negative ttl and 404

2009-10-08 Thread Ramon Moreno
Is there a way to force a minimum age on 404 errors? We have a
situation where it appears 404s are getting cached, and squid is
honoring the TTLs of the webserver (could be hours/days). So the 404s
persist after the default negative ttl of 5 minutes.

Can we force this to 5 minutes regardless of the TTL that is passed by
the webserver?

Maybe an acl/refresh pattern or something? Didn't see anything for 404s.

Thanks!


Re: [squid-users] negative ttl and 404

2009-10-08 Thread Amos Jeffries

Frank Ruiz wrote:

Is there a way to force a minimum age on 404 errors? We have a
situation where it appears 404s are getting cached, and squid is
honoring the TTLs of the webserver (could be hours/days). So the 404s
persist after the default negative ttl of 5 minutes.

Can we force this to 5 minutes regardless of the TTL that is passed by
the webserver?

Maybe an acl/refresh pattern or something? Didn't see anything for 404s.

Thanks!


negative_ttl should be 0 seconds for HTTP compliance.

No there is not way in current Squid to cap objects storage times to 
less than a year.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE7 or 3.0.STABLE19
  Current Beta Squid 3.1.0.14