Closed Bug 318578 Opened 19 years ago Closed 19 years ago

Regression - NTLM Proxy authorization requested for every page in FF1.5, only requested once per session in FF1.0.x

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 318253

People

(Reporter: kenh, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Build Identifier: http://download.mozilla.org/?product=firefox-1.5&os=win&lang=en-US Using Firefox through an NTLM proxy (MS Proxy Server). It may be significant that this proxy is a member (and not the domain controller) of a Windows 2003 domain.....and thus the username must be entered as domain\username. After starting FF1.0.x, when the first page is requested through the proxy, it prompts for username and password. After this, everything works normally. (This is the same behaviour as IE6) In FF1.5, for every request to the proxy, (even each image on a page), it prompts for username and password. Enabling the password manager, and checking the "Remember this password" box in the Proxy Authentication dialog improves things slightly.......the username and password are automatically filled in each time the dialog appears, but one still has to click ok/hit enter. Reproducible: Always Steps to Reproduce: 1. Configure Firefox 1.5 to connect to the internet via a Microsoft Proxy Server using NTLM authentication. 2. Start browser 3. Access external websites Actual Results: As mentioned above....the user is prompted for Proxy username and password for each http request. Expected Results: The expected behaviour should be what Firefox 1.0.x does, i.e. prompt for the password once, then remember it for the rest of the session. Choosing a severity of "Major", since this problem effectively makes FF 1.5 unusable in this situation.
*** This bug has been marked as a duplicate of 318253 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.