[squid-users] TCP_REFRESH_MODIFIED

Amos Jeffries squid3 at treenet.co.nz
Wed Nov 4 09:41:12 UTC 2015


On 4/11/2015 11:38 a.m., joe wrote:
> at least you pay attention on "gvs" :) +1
> 
> lets forget about youtube    :)  im just asking why TCP_REFRESH_MODIFIED if
> i don't or did not force reload
> ignore-privet its working but ignore-reload its not .. suppose to prevent
> TCP_REFRESH_MODIFIED from hapening right ?

No, ignore-reload means ignore the Ctrl+F5 / reload button headers
received from clients (if any). It has nothing to do with the server
response details.

> 
> and talking about private control its used for public control now not just
> privet content
> 

The design model for Squid caching is "shared cache". Which means
strictly following RFCs Cache-Control:private content is not allowed to
be stored. Doing so in a shared cache design causes big problems.

We get around that danger in Squid by doing the revalidations. For most
traffic it should work find and reduce bandwidth. For some it does not.
But the worst-case there is no different from the proxy having done what
was mandatory to do in the first place.

Amos



More information about the squid-users mailing list