Search squid archive

Re: Squid3 reverse proxy ntlm authentication

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/10/2012 6:50 a.m., muno wrote:
The only error i get is:

1349294400.422    429 200.220.102.34 TCP_MISS/401 2171 GET
http://warpx.uninet.c
om.br/ - FIRSTUP_PARENT/200.220.0.103 text/html

Backend peer requesting login credentials from Squid.

The Squid login=PASS configuration sends Basic auth credentials between Squid and the peer. If you are doing NTLM between Squid and the client then Squid will only have the username available to send, no password. Your peer needs to support that, OR you need to locate credentials elsewhere (eg an external ACL helper), OR you need to specify a login for Squid to use on its requests to the peer.



AND

349354025.463      0 200.220.102.34 TCP_DENIED/401 4014 GET
http://warpx.uninet
.com.br/favicon.ico - HIER_NONE/- text/html

Either auth starting or NTLM handshake token challenge request between client and Squid.



Just for my understanding. I need authenticated browser and
squid passing credentials. I don't know if the path that i
am trying is correct. am I correct?

The Squid portion seems to be working. The top request was authenticated and sent through Squid to the peer. Unfortunately the peer does not accept it.


Amos



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux