[squid-users] Strange problem with bluecoat and login=PASS

Users authenticate on out local proxy. Squid should pass this authentication
to a parent proxy (Bluecoat).

Using

    cache_peer frd-proxy parent 8080 3130 login=PASS no-query
                                          -----------

users can access internet, but after some hours (4 - 12 hours?) they get the
error message

     Access Denied (policy-denied)

Then internet access is denied for all pages and for all users.

If I replace the above statement by

   cache_peer frd-proxy parent 8080 3130 login=userxy:topsecret no-query
                                         -----------------------

the error above does not occur.

Question: Is there a difference squid handles "login=PASS" different from
"login=userxy:topsecret"?

# sq version
Squid Cache: Version 2.5.STABLE7
configure options: --enable-auth=ntlm,basic
--enable-external-acl-helpers=winbi
nd_group --enable-basic-auth-helpers=winbind
--enable-ntlm-auth-helpers=winbind
--prefix=/usr/local/squid --with-samba-sources=/usr/local/samba-2.2.5
#

The administrators of the bluecoat proxy do not see any errors in their
logfiles though the error message above obviously is generated by bluecoat.

Has anybody seen this behaviour too?

Werner Rost
Received on Fri Feb 04 2005 - 03:32:01 MST