Closed
Bug 701362
Opened 14 years ago
Closed 9 years ago
Prompt for authentication being displayed on refresh
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: thittesd0375, Unassigned)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243
Steps to reproduce:
The following code executes on child window close:
<body onbeforeunload='javascript:opener.location.reload(true);'>
Actual results:
The parent window periodically asks for the login information. Sometimes multiple times for one refresh. The site is secured with NTLM authentication.
Setting network.automatic-ntlm-auth.trusted-uris prevents the dialog on Win 7 but doesn't on Win XP and OS X.
Expected results:
The page should refresh with the cached session.
Reporter | ||
Updated•14 years ago
|
Severity: normal → major
OS: Mac OS X → Windows XP
Comment 1•14 years ago
|
||
I can confirm this happening to our tools as well on Windows 7.
Any ASP.Net MVC3 web apps using Windows Authentication will get the authentication prompt on FF8 but not in any other browsers (FF 7 also works fine for those that have not yet updated)
Comment 2•14 years ago
|
||
So just to be clear, this is a new problem that started occurring on upgrade to Firefox 8?
If so, would you be able to help test nightly builds and try to determine a more precise regression range?
Component: Account Manager → General
Product: Firefox → Core
QA Contact: account.manager → general
Comment 3•14 years ago
|
||
I would not be able to test at night, but I can squeeze in some test builds in the morning.
Comment 4•14 years ago
|
||
Sorry, by "test nightly builds" I meant "test the builds that we produce daily (at night)". They're available for download at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ , and using binary search it should hopefully be not too hard to isolate the regression to a 1-day window of changes, which should help identify the root cause.
The tricky part is knowing which range to start with. I can help with that if you can confirm that Firefox 7 works, but Firefox 8 doesn't.
Reporter | ||
Comment 5•14 years ago
|
||
I've tested the Mac versions of 7.0.1 and 8.0 b1-b6. The problem is not present on the 7.0.1 build but is present in all 6 beta builds for 8.0. I'll take some time tomorrow and go back further and see if I can't find a 8 build that works.
Reporter | ||
Comment 6•14 years ago
|
||
The behavior is not present in this build:
ftp://anonymous@ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2011/07/2011-07-25-03-08-03-mozilla-central/firefox-8.0a1.en-US.mac.dmg
The behavior is present in this build:
ftp://anonymous@ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2011/07/2011-07-26-03-08-25-mozilla-central/firefox-8.0a1.en-US.mac.dmg
Comment 7•14 years ago
|
||
Comment 8•14 years ago
|
||
The only entry in that list that looks to have any relation would be bug 628561, which forces clearing persistent connections on reload.
Blocks: 628561
Updated•14 years ago
|
Keywords: regression
Comment 9•14 years ago
|
||
I kinda have a meh reaction to this one. ntlm authenticates the http connection and http connections can be closed at any time.
That pref should certainly behave the same on all builds though. We should figure out the issue underneath that, but that's unlikely to be a regression.
Comment 10•14 years ago
|
||
The issue is still occurring on the 9.0.1 version released today.
Comment 11•9 years ago
|
||
This bug has been tagged for regression and or closure.
It is working as expected in Release & Nightly
Version 45.0.1
Build ID 20160315153207
User Agent Mozilla/5.0 (Windows NT 5.1; rv:45.0) Gecko/20100101 Firefox/45.0
Version 48.0a1
Build ID 20160405030214
Considering this I will mark this issue as Resolved-WORKSFORME.
If anyone can still reproduce it, feel free to reopen the issue and provide updated steps/links.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•