Closed Bug 407268 Opened 18 years ago Closed 17 years ago

upon session restore, don't prompt for http auth for background tabs

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 516781

People

(Reporter: moco, Unassigned)

References

Details

upon session restore, don't prompt be to do http auth steps to reproduce: 1) visit a site that requires http auth, like https://intranet.mozilla.org/Main_Page, log in 2) open 5 more tabs to https://intranet.mozilla.org/Main_Page 3) open a 6th tab to google.com 4) quit the browser, and make it so you restore on startup actual results: on startup, I get 5 http auth prompts, one after another. expected results: only one auth prompt (if the selected tab requires it) or none, if google.com comes up selected perhaps this could be a general bug: "don't issue http auth prompt unless tab is selected?" As, you could imagine a tab in the background doing a redirect to a page that requires auth, stealing my attention from what ever I'm doing.
What should we do instead? Fail to load the page?
> What should we do instead? Fail to load the page? good question. say I had 5 tabs open to gmail.com. if they loaded in the background and I wasn't authenticated, I'd get sent to the gmail login page. maybe for tabs not selected we should act like the user hit cancel? When I go to that tab, I'd see something like: Authorization Required This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required. Note, if what I am proposing breaks the web, feel free to wontfix. I just find it really painful to restore when this bug hits me.
I know that in some cases, if we "cancel" the prompt, some servers won't let you try to login again for that session. I think this might be a duplicate of bug 348997, but I'm not sure. A lot of the dupes of that bug seems similar to this one, but some of the comments mention weird master password interactions.
This is probably rather a dupe of bug 339804, although the symptoms are the same.
All these bugs (bug 396693, bug 338549 too) were, afaik, as result of fixing bug 326273 (nsIThreadManager). Whereas we previously blocked when a user-input prompt was displayed, now we don't. This leads to getting multiple prompts, sometimes for the same thing, when lots of stuff is loading. I'm not sure what the right way to fix this is, especially since we're late in the 1.9 cycle.
I think this bug is resolved by bug 475053.
Depends on: 475053
Whiteboard: [fixed by bug 475053?]
Well, not entirely. There are two issues in this bug: 1) Getting multiple prompts for the same site loaded in multiple tabs 2) Not showing an HTTP auth prompt for background tabs. Bug 475053 does indeed fix the first issue. I think the second issue was originally mentioned as a way to workaround the first issue, but it's still relevant. Basically, it's the HTTP auth equivalent of bug 513534... If you just started the browser, it's likely that you want to go do something, not be forced to deal with a number of HTTP auth prompts for tabs you're not interested in at the moment. Bug 223636 will also help here, in that if the login is automatic you won't be prompted (although there's still the possibility of triggering a master password, ala bug 513534).
Whiteboard: [fixed by bug 475053?]
What about switching these prompts to content area messages instead of dialogs.
I think this bug got too confused; I extracted the useful information into bug 516781 and duping this one over to the new one.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.