Quin Guin wrote:
Hi,
I am seeing a behavior with the negative_ttl option and I would like to get
confirmation on its behavior.
I am using 2.7.Stable6
I am having an issue with a content provider that is setting the max_age=604800
on 503 error pages and so their 503 error pages are getting cached for the
length expire time.
If it's just 503's you are having trouble with...
acl HTTPStatus503 http_status 503
cache deny HTTPStatus503
...will deny caching of any response with a 503 code. Fine tune it with
an additional dstdomain acl as needed.
I know that the content provider should correct this and I have communicated
that to them several times but it gets fixed and then it gets set again..ugh!!
So everyone saying SQUID has a bug or broke..
I have set the "negative_ttl 0" in hopes that the negatively cached pages doesn't get cached at all not even for the default 5 min. This works for pages that don't have max_age values or very low ones.. I just want to confirm that this is the expected behavior for negative_ttl.
If so I think my next course of action in the 2.7 build line is to use and acl
with deny on http status values? If anyone has done this and would like to
share what they did or can point me to some docs or something similar I would
appreciate that.
I know 3.1 have the ability to do what I need but I am not ready to roll that
out to production yet.
Thanks,
Quinguin
Chris
