On 9/05/2013 1:17 p.m., Brett Lymn wrote:
I have been chasing down problems with squid ever since I updated to
v3.3.2. I have found one that looks a lot like a bug with the acl
matching. I have a particular IP address that people here are trying to
access that we cannot access because a cache
I have been chasing down problems with squid ever since I updated to
v3.3.2. I have found one that looks a lot like a bug with the acl
matching. I have a particular IP address that people here are trying to
access that we cannot access because a cache peer is not selected. I
use
I'm using the fallowing segment of configuration in our squid.conf to
archive some spreading across several IP's to minimize some limitations
imposed by some sites by IP address (traffic, simultaneous access,
etc)
acl outaddr1 src 0.0.0.0/0.0.0.3
acl outaddr2 src 0.0.0.1/0.0.0.3
acl outaddr3 src
Esteban Ribicic wrote:
is there any pratical way to distinbguish if acl's are matching?
thx
Esteban
Euhmincrease the logging.
Bart
