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

I believe there were some bugs fixed regarding caching in 3.4.4. I noticed better cache hits after upgrading to the 3.4.4 version. I am now running 3.4.4.2 since there was a connect bug also fixed in this version.

Best regards,
The Geek Guy

Lawrence Pingree
http://www.lawrencepingree.com/resume/

Author of "The Manager's Guide to Becoming Great"
http://www.Management-Book.com
 

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Monday, April 28, 2014 10:14 AM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Cache-Control: public doesn't cache

On 29/04/2014 4:19 a.m., Rob van der Putten wrote:
> Hi
>
>
> AFAIK 'Cache-Control: public, no-transform' is cacheable. But Squid
> (3.3.8) doesn't cache.
>

That one header does not make it cacheable...
 * "no-transform" has no meaning at all in regards to cacheability.
 * "public" is only meaningful when authentication is being used.

... in HTTP/1.1 everything is considered cacheable unless the protocol defines a reason not to.

Squid may choose not to cache for many other reasons related to the request headers, response headers, server trustworthiness, age of the object on arrival, and available storage space.

Some reasons in the protocol are broad, like "a response to an unknown method is not cacheable". **

Others are very specific, like "a cached object with Cache-Control no-cache or must-revalidate may only be used as a response after a successful revalidation (304 not modified) from the origin server." **

** very rough paraphrasing by me.

Amos
Received on Tue Apr 29 2014 - 04:06:50 MDT