[squid-users] NOTICE: Authentication not applicable on intercepted requests.

Eugene M. Zheganin emz at norma.perm.ru
Thu Jun 30 19:19:54 UTC 2016


Hi.

On 30.06.2016 17:04, Amos Jeffries wrote:
> On 30/06/2016 9:21 p.m., Eugene M. Zheganin wrote:
>> Hi,
>>
>> Could this message be moved on loglevel 2 instead of 1 ?
>> I think that this message does 95% of the logs of the intercept-enabled
>> caches with authentication.
>>
>> At least some switch would be nice, to switch this off instead of
>> switching the while facility to 0.
> This message only happens when your proxy is misconfigured.
Well, it may be.

> Use a myportname ACL to prevent Squid attempting impossible things like
> authentication on intercepted traffic.

Sorry, but I still didn't get the idea. I have one port that squid is configured to intercept traffic on, and another for plain proxy requests. How do I tell squid not to authenticate anyone on the intercept one ? From what I know, squid will send the authentication sequence as soon as it encounters the authentication-related ACL in the ACL list for the request given. Do have to add myportname ACL with non-intercepting port for all the occurences of the auth-enabled ACLs, or may be there's a simplier way ?

Thanks.
Eugene.



More information about the squid-users mailing list