Comment #6 on issue 8325 by [email protected]: NTLM authentication to a proxy doesn't work if Privoxy sits in between http://code.google.com/p/chromium/issues/detail?id=8325
igitur: thanks for posting the error log. This confirms my suspicion. First, you said build 2.0.166.1 (current DEV release) doesn't have this problem. But build 2.0.166.1 does NOT support NTLM! So build 2.0.166.1 must have used a non-NTLM auth scheme with your company proxy. We can verify this using the message in the login dialog. Does it say "The server xxx at xxx requires a username and password." or "The server xxx requires a username and password." ? Chromium uses the second message (without "at xxx") for NTLM. If build 2.0.166.1 uses the first message, then it's using a non-NTLM auth scheme. The following are some comments on the NTLM problem with the latest build. Chromium's HttpResponseHeaders::IsKeepAlive function looks at the Proxy-Connection response header only if there's no Connection response header. The error log shows that both headers are present, so we base our decision on the "Connection: close" header, even though the "Proxy-Connection: Keep-Alive" header says the opposite thing. The Mozilla code also gives the Connection response header precedence over the Proxy-Connection response header: http://bonsai.mozilla.org/cvsblame.cgi? file=mozilla/netwerk/protocol/http/src/nsHttpConnection.cpp&rev=1.63#295 So we still don't know why Firefox works. Perhaps it chooses a non-NTLM auth scheme? Please type "about:config" into the Firefox location bar, and then type "ntlm" into the Filter field. What are the values of the three NTLM-related Firefox preferences? What is the message in Firefox's login dialog for your company proxy? When I did a web search for "Privoxy NTLM", I found an old bug report of Privoxy NTLM problem in 2007: http://osdir.com/ml/web.privoxy.user/2007-07/msg00038.html http://sourceforge.net/tracker/?func=detail&atid=211118&aid=1760018&group_id=11118 I think that bug report is the same as the problem you're experiencing. Could you check your Privoxy log to see if you also have messages similar to these from that bug report? Jul 24 15:08:14 Privoxy(000015f4) Header: crumble crunched: Proxy-Connection: Keep-Alive! Jul 24 15:08:14 Privoxy(000015f4) Header: Adding: Connection: close -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
