Well, i haven't made the update in the ticket, but i found a solution
some time ago.
If you migrate from 2.5 to 2.6 the way squid analices the acls changes
when an acl has a refernce to a username or group. Every acl that has
a to check username/password or membership of a group re ask for
authentication credentials.
If you have:
http_access allow mygroup
http_access allow myuser
http_access allow workhours workers
http_access allow seconduser
Every http_access ask for authentication credentials and this
generates a lot of load and traffic to the authenticator.
To avoid this, is necesary to create the acls like this:
acl dummy src 0.0.0.0/0.0.0.0
http_access allow mygroup dummy
http_access allow myuser dummy
http_access allow workers workhours
http_access allow seconduser dummy
This way, the "dummy" acl is the one that denies (or not) the traffic,
and this way it dosen't ask for credentials again...
Hope this helps closing the ticket.
Tnxs.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
