PROTECTED]
To: Elli Albek [EMAIL PROTECTED]
Cc: squid-users@squid-cache.org
Sent: Sat, 18 Oct 2008 21:25:32 -0700 (PDT)
Subject: Re: [squid-users] Why are cache_peer_access acls called 4 times in a
row?
Elli Albek wrote:
Hi,
I have a simple setup for testing accelerator:
http_port 127.0.0.4
On sön, 2008-10-19 at 17:25 +1300, Amos Jeffries wrote:
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):
What is the reason for that? Other acls in the file are invoked only once
(seen in the trace), but acls on
Thanks.
It makes sense since setting always direct to this acl evaluates the acl once
(and also once on the always direct rule, but this is expected).
The four acl evaluations return success, so is it possible to configure squid
to stop at the first success or just evaluate one algorithm?
E
On sön, 2008-10-19 at 17:12 -0700, Elli Albek wrote:
It makes sense since setting always direct to this acl evaluates the acl
once (and also once on the always direct rule, but this is expected).
The four acl evaluations return success, so is it possible to configure squid
to stop at the
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
Elli Albek wrote:
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
