I've tried almost all options for cache_peer but it doesn't seem to work. Is it a squid's bug? Eric NGUYEN DANG LUAN -----Message d'origine----- De : NGUYEN DANG LUAN, Eric [mailto:eric.nguyen-dang-luan@xxxxxxxxxx] Envoyé : lundi 6 octobre 2008 09:29 À : Henrik Nordstrom Cc : squid-users@xxxxxxxxxxxxxxx Objet : RE: Squid with webwasher using NTLM authentication >> When a user is connect directly on webwasher it works. He is authenticated worretly (I can see that thanks to logs). >> But once I implement a Squid cache server, it doesn't work. My user can't be authenticated. >Have you told Squid to trust the webwasher proxy with proxy login credentials? See cache_peer directive. I'm currently using this line: cache_peer comp parent 3128 3130 no-query default For the moment there is no login credentials. I'm gonna check this. Regards, NGUYEN DANG LUAN Eric -----Message d'origine----- De : Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Envoyé : samedi 4 octobre 2008 16:14 À : NGUYEN DANG LUAN, Eric Cc : squid-users@xxxxxxxxxxxxxxx Objet : Re: Squid with webwasher using NTLM authentication On fre, 2008-10-03 at 10:17 +0200, NGUYEN DANG LUAN, Eric wrote: > I'm using squid as a cache server working with webwasher (proxy + authentication + webpage filter). Here's the context : > > User's computer<---->Squid <----> Webwasher<--->Internet > | > | Authentication > |(Using NTLM) > | > NTLM > Agent > > When a user is connect directly on webwasher it works. He is authenticated worretly (I can see that thanks to logs). > But once I implement a Squid cache server, it doesn't work. My user can't be authenticated. Have you told Squid to trust the webwasher proxy with proxy login credentials? See cache_peer directive. > Does anyone has an idea? I'm using squid 2.6 running on a RedHat linux server 5. Maybe you need to upgrade to 2.7. But it depends on which exact 2.6 release you are using.. see below. > Right now i'm trying squid 3 but it dosen't seem to work too. squid-3.0 does not support forwarding of NTLM authentication as it does not yet implement the required workarounds to Microsoft HTTP protocol violations needed to support NTLM forwarding. Regards Henrik
