User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Imagine a page with 1000 images that require HTTP AUTH. Right now, if you click 'Cancel' for the first one, it will still popup the dialog another 999 times. Reproducible: Always Steps to Reproduce: 1. Go to a webpage with lots of images behind an HTTP auth 2. Get the auth wrong or click cancel 3. Get **** about having to keep clicking cancel. Actual Results: Lots of popups. Expected Results: Popups stop.

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2007122604 Minefield/3.0b3pre ID:2007122604 This happens if you have specified an error document with a lot of referenced images. If you cancel the http auth prompt you get redirected to that page and have to click through all the prompts - one for each image. It can easily reproduced by putting a .htaccess file into the root of a (sub)domain. The error page should be located under this folder which is normal. Try to access the domain and cancel the http auth prompt. As example you can use http://devel.hskupin.info/. We shouldn't ask for a password after an unsuccessful/canceled login.

I had something similar happen to me due to a glitch at pajamasmedia.com during their format change. Viewing their page popped up a password dialog box that just would not go away and as a result there was no way to leave that page or even exit Firefox without resorting to Task Manager.

I get similar error when I try to view a page which includes multiple images that resides in a folder which is protected by http auth. I receive one master password login prompt for every protected image, eventually resulting in max CPU-load and browser death. This wasn't the case with version 2.x of the Firefox browser. I am really looking forward to a fix.

(In reply to comment #3) > I receive one master password login prompt for every protected image, > eventually resulting in max CPU-load and browser death. I think mine was a dup. of https://bugzilla.mozilla.org/show_bug.cgi?id=356097