[squid-users] Squid 4.2 : caching is not working

Amos Jeffries squid3 at treenet.co.nz
Mon Sep 10 14:50:59 UTC 2018

On 11/09/18 2:27 AM, Hariharan Sethuraman wrote:
> On Mon, 10 Sep 2018, 19:46 Amos Jeffries wrote:
>     On 11/09/18 12:18 AM, Hariharan Sethuraman wrote:
>     >  
>     > 2) With more debug_options enabled, I see that it is not caching
>     because
>     > the response is part of authenticated flow. Is there a way I can
>     > override this?
>     No. The server is supplying sufficient headers for caching to make it
>     appear that the site authors intentionally are sending what does get
>     delivered.
> If I understand correctly, you are saying the caching will not be done
> on squid as the content is authorised by the specific client. We can't

Authenticated, not authorized. This is one place where the difference

> do anything until I ask site owners to change cache control as public?

Pretty much, yes. I know Chrome at least used to deliver binaries whose
installer contained details of the Google account of the user fetching
it. So its not very safe to assume even downloaders are safely transferable.


More information about the squid-users mailing list