[squid-users] Why are cache_peer_access acls called 4 times in a row?

Hi,
I have a simple setup for testing accelerator:

http_port 127.0.0.4:80 accel defaultsite=1.2.3.4:80
cache_peer 1.2.3.4 parent 80 0 no-query originserver name=parent_sl
acl my_acl urlpath_regex ^/rev/
acl port80 port 80

http_access deny !port80
http_access allow port80
cache_peer_access parent_sl allow my_acl

There are no other acls and configuration except from what is in the base
squid.conf.default.

When I request a URL from squid I can see in the trace that the acl "my_acl"
is executed 4 times consecutively. This acl is only used in
"cache_peer_access parent_sl" once and in no other place.

The following trace shows up in the log 4 times one after the other, and in
all of them it is a success (returning 1):

aclCheckFast: list: 003CA058
aclMatchAclList: checking my_acl
aclMatchAcl: checking 'acl my_acl urlpath_regex ^/rev/'
aclMatchRegex: checking '/rev/288/scripts/v2/lib/util.js'
aclMatchRegex: looking for '^/rev/'
aclMatchRegex: match '^/rev/' found in '/rev/288/scripts/v2/lib/util.js'
aclMatchAclList: returning 1
aclCheckFast: list: 003CA058

What is the reason for that? Other acls in the file are invoked only once
(seen in the trace), but acls on cache_peer_access are always called 3 or 4
times.

Thanks

Elli
Received on Sun Oct 19 2008 - 01:52:50 MDT