Closed Bug 249762 Opened 21 years ago Closed 21 years ago

Firefox shows htaccess password entry prompt on startup when favicon is protected by htaccess

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 133755

People

(Reporter: prasenjeetd, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Lightningimpala/0.9 (Firefox/0.9) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Lightningimpala/0.9 (Firefox/0.9) 1. I have a intranet-accessible server http://internal.foo.com/ that's protected by Basic authentication (AuthType Basic on Apache). 2. It has a favicon, http://internal.foo.com/favicon.ico. 3. Firefox is set to "Use Blank Page" as its homepage. 4. A bookmark in Firefox's "Bookmarks Toolbar Folder" points to http://internal.foo.com/. Reproducible: Always Steps to Reproduce: 1. Launch Firefox by double-clicking its shortcut icon on the desktop, or by another means. Actual Results: 1. Firefox opens and shows the home page (blank in this case). 2. Almost immediately, I see Firefox's Basic/Digest authentication dialog asking me to enter the username/password for the internal.foo.com realm. 3. I notice that the favicon for the internal.foo.com bookmark in the Bookmarks Toolbar Folder is not visible. 3. Since I am using Password Manager, I just press OK to enter the username/password automatically. 4. Once I press OK, the dialog goes away. The favicon for the internal.foo.com bookmark in the Bookmarks Toolbar Folder is now *visible*. Expected Results: Firefox should have just opened the home page and not shown the authentication dialog on startup. 1. I am using Firefox 0.9.1. 2. It's highly irritating to have that dialog pop up every time one starts the browser. Can this one please be reprioritized "Major"?
*** This bug has been marked as a duplicate of 133755 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.