[squid-users] delay_pools from 3.1 to 3.4

[Amos Jeffries]

On 4/12/2015 12:40 a.m., Massimo.Sala at asl.bergamo.it wrote:
> Squid 3 as forwarding proxy, intranet LAN.
> 
> We want to limit the bandwidth only for multimedia content.
> 
> On 3.1.20 we have these lines into squid.conf :
> 
> acl localnet src 10.0.0.0/8
> 
> acl acl_flussi_media rep_mime_type -i ^audio/
> acl acl_flussi_media rep_mime_type -i ^video/
> 
> delay_pools 1
> delay_class 1 1
> delay_parameters 1 320000/320000
> delay_access 1 allow acl_flussi_media
> delay_access 1 deny all
> 
> http_access allow localnet
> http_access deny all
> 
> 
> Using the same lines on the new server, with squid 3.4.8, we got these 
> warnings in cache.log :
> 
>         2015/12/03 12:38:45 kid1| WARNING: acl_flussi_media ACL is used in 
> context without an HTTP response. Assuming mismatch.
> 
> 
> What does it mean ? How to fix it ?

It means that *reply* header do not work when using *request* to decide
what delay pool the transaction will use.

It has never worked. The older Squid just did not tell you about the
config problem.

If you want traffic to be re-assigned to pools when the reply happens
you need to upgrade to at least the Squid-4.0.3 (beta) release.

Amos