Re: [squid-users] http 302 status and storeid: infinite loop problem

On 9/10/2013 10:32 a.m., Eliezer Croitoru wrote:
> On 10/08/2013 10:45 PM, Nikolai Gorchilov wrote:
>> That's why it is necessary to have an acl clause that prevents Squid
>> from caching a page based on contents of the response headers,
>> especially status code.
> Hey,
>
> Or just let server admins put the right headers for the right objects..
> A simple header can mean that the response in not cachable..

Indeed such temporary redirect messages should be given a
Cache-Control:no-store header.
Otherwise the service is unlikely to recover quickly once the
maintenance redirect is removed.

Not much we can do about it though if the admin does the wrong thing.

> ho and by the way YT videos are cachable by defalut... no need to
> force too much refresh_patterns..
>
> Eliezer

I have opened http://bugs.squid-cache.org/show_bug.cgi?id=3937 to track
this.
The ACLs have some problems detecting this, but I think we should be
able to come up with a code solution that can be built into Squid for
default use.

Amos
Received on Wed Oct 09 2013 - 04:59:24 MDT