[squid-users] Config changes between 2.7 and 3.5

[Amos Jeffries]

On 29/06/2016 9:19 a.m., Bidwell, Christopher wrote:
> Hi all,
> 
> I'm trying to find what's used to replace these:
> 
> squid 2.7                           squid 3.5
> --------------------------------------------------
> zero_buffers                      ???

An experiment in 2.7. It ceased to be an experiment a while back and the
directive to disable was dropped.


> refresh_stale_hit               ???

This Squid-2 feature has been superceeded by the HTTP/1.1
stale-while-revalidate mechanism at the protocol level. So a port to
Squid-3 is not planned.

But Squid-3 does not implement the stale-while-revalidate yet.

There is currently some work underway an Measurement Factory to make the
Squid-3 collapsed_forwarding feature operate properly with revalidation,
which will get halfway there.

If you need this directives behaviour and would like to assist with
development, testing, or sponsorship please drop a message in to
squid-dev mailing list.


> ignore_ims_on_miss         ???

The behaviour of this directive was a naive and simplistic duplicate of
the request_header_access directive with a very limited amount of
usefulness.

Consider removal, but if you need the behaviour still use
"request_header_access If-Modified-Since deny all" instead.

The request_header_access is also more powerful in that it is ACL driven
and can strip other If-* headers as well for other types of IMS/INM request.

Amos