User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5a) Gecko/20030702 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5a) Gecko/20030702 Mozilla Firebird/0.6 while going through a proxy that requires authentication and visiting a site that uses basic auth, mozilla will get confused and start popping up prompts to authenticate with the proxy and then back again with the site over and over again. Reproducible: Always Steps to Reproduce: 1. setup proxy with auth 2. visit site with basic auth 3. Actual Results: mozilla will get confused and start popping up prompts to authenticate with the proxy and then back again with the site over and over again. Expected Results: granted access through the proxy and to the site without repeatedly prompting for username/pass proxy used in this case is ms proxy 2.0, but i doubt that matters

are you using NTLM auth on MS Proxy 2.0 ? can you attach a log ? See instructions here: http://www.mozilla.org/projects/netlib/http/http-debugging.html

not really a patch but i couldnt otherwise upload it..sorry. and yes, NTLM with MS Proxy 2

couldn't find similar bugs (i.e. dupes), marking NEW since it has a log. Does the basic auth reset for internal sites or every public site too ?

unfortunately i dont have any internal sites (nor access to our internal servers) to test this on.

i see the bug from the log file... i'll try to get this fixed for moz 1.5.

hmm... ok, i looked over the log file some more, and here's what's going on: the server is closing the socket connection before we have completed the NTLM handshake. we detect the closure and try on a new socket, but we don't restart the NTLM handshake properly. as a result, the NTLM handshake seems to fail, and when login fails, we clear the login credentials. we need to restart the NTLM handshake when we hit this condition. but, that said... this is really a bug in your proxy server because it shouldn't be closing the connection prematurely like this. if possible you should try to get it upgraded because even if i fix this bug in mozilla, you'll still get poor performance from your proxy server.

My NTLM proxy server is down, but I'm pretty sure that I've tested this combination (proxy auth w/ NTLM to web w/ basic auth). I'm finding out the hard way from the buster worm that Microsoft does not think much of supporting Proxy 2.0 anymore, especially since it is typically run on Windows NT 4 Server. Darin, if you want me to look at this further, let me know, b/c I have to budget time after work to look at this, but I'd be happy to w/ a little advanced warning.

thanks ben, but at the moment i have all the info i need from the HTTP log file. i just have to figure out the best way to code up the solution ;-)

*** Bug 220037 has been marked as a duplicate of this bug. ***

punt

btw: In Bug 278885 a potential patch was posted. Maybe someone wants to take a look at it?

reporter's address is dead. opting to dup to bug 278885. feel free to => incomplete or reopen if you disagree