Re: [squid-users] Re: Cache-Control: public doesn't cache

On 29/04/2014 7:36 p.m., Rob van der Putten wrote:
> Hi there
>
>
> Amos Jeffries wrote:
>
>> http://redbot.org/?uri=http%3A%2F%2Fsput.home.xs4all.nl%2F
>>
>> Results are the same for both.
>>
>>
>> Fatal problem breaking caching:
>> * The ETag doesn't change between negotiated representations.
>>
>>
>> Squid refresh_pattern heuristics are a bit odd and dont deal with very
>> old objects well. these might (or not) be an issue:
>> * The resource last changed 1 year 221 days ago.
>> * This response allows a cache to assign its own freshness lifetime.
>>
>>
>> Useless cruft in the server output:
>> * Cache-Control: public is rarely necessary.
>
> AFAIK, it's meaningless in this context.
>
>> * Vary: Host is not necessary.
>
> Squid 3.1.20 considers this stuff to be cacheable. 3.3.8 doesn't.
> But 3.1.20 won't do a IPv4 fallback.

Aha! 3.3 has a Vary bug. Please try 3.3.12, 3.4.4, or the latest 3.4
snapshot.

Amos
Received on Tue Apr 29 2014 - 08:49:44 MDT