(same initial steps as bug 113021, but with one change in profile configuration, which results in a duplicate /favicon.ico request being issued). 1) create a new profile (i.e., all default settings) 2) set the profile to open new windows with a blank 3) quit browser 4) _delete_ the cache folder 5) start browser and load http://cowtools/ -- this will create the disk cache again with three entries: one for the cowtools document, one for a gif in that page, and one (negative) for the cowtools/favicon.ico 6) the change from the other test setup ... Edit->Preferences->Navigator->Tabbed Browsing -- uncheck 'Hide the tabs bar when only one tab is open' -- Ctrl-T -- click X to close the new tab 7) shut down the browser 8) start browser 9) Enter 'http://jrgm.mcom.com/' in the urlbar and hit enter -- this makes three HTTP requests: - one for the top level document - two (one duplicate) requests for /favicon.ico (presumably one for the proxy icon, and one for the tab icon) To see the request log, telnet to jrgm and 'tail /etc/httpd/logs/access_log'

This should be a dupe, and I get it even without tab bar always. Example: GET /page.html <--- page.html has a <link rel=icon href=/icon.png> GET /favicon.ico <--- should never have been GET /icon.png GET /favicon.ico <--- probably trying to find the icon to use for /icon.png So basically, what should have been 1 GET without icons, turned into 4. Looking for dupe material.

Aw, c'mon. Quit making irrelevant comments. Did I mention _anything_ about dealing with <link ...> in my comments above? Answer: No. Reason: because this has _nothing_ to do with <link ...> elements. This is a simple test case for a particular user configuration. The steps to reproduce still apply, and they apply exactly as originally described. This bug, to my knowledge, is not a duplicate of any other bug. (Of course, we could just lump each and every bug that so much as mentions "favicon.ico" into a single, complicated, unreproducible, rambling bug report. But then again, maybe that's not a very bright idea.)

I think you misunderstood. My page has a link rel=icon, and I still get the duplicate requests you filed this bug for. I was simply providing a secondary testcase (one outside of "The Firewall", to boot).

No, you misunderstand. My point was precisely that this bug has _nothing_ to do with "<link rel...". Of course, I already said exactly the same thing in my previous comment. It is irrelevant to the purpose of _this_ bug that you can get redundant GET request issued "some other way". ... and now, this bug report is begin to degenerate into the type of rambling, argumentative, contradictory, and "what the hell am I supposed to fix?" bug report that wastes so much of developer's time. Seriously. There is nothing more that needs to be said on this bug report, other than "this bug is fixed/verified" [due to a code change] or "this bug is worksforme" [from retesting of the originally stated steps to reproduce].

Is this happening with current builds?

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420