Closed Bug 266303 Opened 20 years ago Closed 20 years ago

If proxy authorization via NTLM fails, password is asked on every file loading

Categories

(Core :: Networking: HTTP, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 256949

People

(Reporter: tonn81, Assigned: darin.moz)

Details

(Whiteboard: [dupe of bug 256949?])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

I use Firefox to access internet sites through Squid that support NTLM
authorization. When i logon in a domain, everything is great - no password is
asked to go to the internet.
But sometimes i go to internet when i work locally, i.e. without logging in a
domain (so my username/password do not match username/password for proxy). Then
NTLM causes many problems - my username/password is asked on EVERY file i load,
even if i enable "Use Password Manager to remember this password".

Reproducible: Always
Steps to Reproduce:

Actual Results:  
Password is asked on every file loading

Expected Results:  
Waring is sent (NTLM authorization failed, please provide correct
username/password). Password is asked only once. Even if i do not use Password
Manager for remembering password!
If we position FF as a replacement for IE, we should fix this unconvenient bug.
Flags: blocking-aviary1.0+
Please test the latest builds off the 1.0 branch:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.11/

I believe this bug may be a duplicate of a solved problem (see: bug 256949)
Whiteboard: [dupe of bug 256949?]
skor, please don't set the blocking plus flag. it is reserved for
drivers@mozilla.org and the Aviary team. thanks.
Flags: blocking-aviary1.0+
Sorry, guys. It's really dupe og bug 256949. ;-)
Night build was no problems.

*** This bug has been marked as a duplicate of 256949 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.