Re: [squid-users] problem with 3.0 and reply_header_access

Leonardo Rodrigues Magalhães wrote:
>
> Hello Guys,
>
> I'm having some problems with Chunk-Decoding and squid 3.0-stable6
> compiled with --enable-http-violations.
>
> Altough i have the rules on my squid.conf:
>
> acl broken1 url_regex -i \.microsoft\.com
> reply_header_access Accept-Encoding deny broken1
>
>
> with debug_options set to ALL,9, i can see the rules getting loaded:
>
> 2008/05/26 15:01:34.460| ACL::~ACL: 'acl broken1 url_regex -i
> support\.microsoft\.com'
> 2008/05/26 15:01:34.491| aclDestroyAccessList: 'reply_header_access
> Accept-Encoding deny broken1'
> 2008/05/26 15:01:34.506| Processing: 'acl broken1 url_regex -i
> support\.microsoft\.com'
> 2008/05/26 15:01:34.506| ACL::FindByName 'broken1'
> 2008/05/26 15:01:34.506| aclParseAclLine: Creating ACL 'broken1'
> 2008/05/26 15:01:34.506| Processing: 'reply_header_access
> Accept-Encoding deny broken1'
> 2008/05/26 15:01:34.506| aclParseAccessLine: looking for ACL name 'broken1'
> 2008/05/26 15:01:34.506| ACL::FindByName 'broken1'
>
> but it cannot seems to be working !
>
> interesting is that browsing cachemgr.cgi, 'Current Squid
> Configuration', i can see NOTHING about reply_header_access rules ....
>
> i'm sure they are there on squid.conf, cache.log seems to show they
> are being loaded, they appear to be NOT working, and they dont appear on
> cachemgr.cgi.
>
> what am i doing wrong ??

Two things.

1) The ACL should be "dstdomain .microsoft.com" not a slow regex.

2) The ACL matches against with request_header_access. The
Accept-Encoding header is only sent from client to server.

Amos

-- 
Please use Squid 2.6.STABLE20 or 3.0.STABLE6