My comments from bug 108809: As for www.dilbert.com, I am getting variable success in showing that icon in the UI. Sometimes it is only in the urlbar, sometimes it's in urlbar and sidebar bookmarks, but not in bookmarks menu, or in personal toolbar bookmarks folder, and sometimes it's in all four places. There is definitely a problem with caching that icon. A request to GET /favicon.ico is being issued on every visit to that page (I can see this in a test proxy server). After some amount of chicken sacrifice, I can sometimes get it to stop requesting /favicon.ico, but regardless the caching does not persist between sessions, and the next time I start the browser, I will repeatedly attempt to GET /favicon.ico from www.dilbert.com. In a mozilla build from 11/30 a.m., the browser was not attempting to GET it on each visit to www.dilbert.com. However, it similarly wasn't persisting between sessions (it would again need to GET /favicon.ico after a browser restart). I can duplicate all of the above behaviour also at http://www.salon.com/. However, in looking at the HTTP headers and the top-level document's content, I don't see anything that would obviously cause problems (although both Salon and Dilbert serve documents with '<meta HTTP-EQUIV="Pragma" CONTENT="no-cache">').

David, any ideas?

Another site w/favicon but won't cache to bookmarks: https://web.da-us.citibank.com/signin/citifi/scripts/start.jsp

I see this on my own site, http://turbogeek.org/. On the main page, I have a link rel=icon href=/icon.png, which it loads. However, it also loads (well, tries to) /favicon.ico. If I reload, it requests /favicon.ico AGAIN. If I follow a link (say, the pgp key one, which is text/plain), it requests /favicon.ico AGAIN. However, the real icon, /icon.png, does stay cached, and is visable in the URL bar and tab. In case this is similar to '113022', my tab bar is set to *not* show, when there is 1 tab. While I was testing the above, there *were* multiple tabs open. This is fairly serious perf and log spam. Linux 2001112808.

Just tested with tabs disabled. Still constantly requesting /favicon.ico.

Pages with '<link rel="icon...' are a _completely_ separate issue. [Perhaps we should just scrap bugzilla and have one bug to which people can append random comments.]

Tried again with todays build and it's no longer requesting /favicon.ico for EVERY page. It does still request it on the first page though, even though there is a <link rel="shortcut icon">. I take it that should be a seperate bug. But perhaps dilbert.com can be rechecked by whoever was having problems there.

This is a dupe of bug 111901. Do a search for favicon and watch the numerous results. I think all of the issues with the favicon have a bug by now.

Given my comment at the end of bug 111901, and the fact that I filed both this bug and bug 111901, then it is pathetically stupid to suggest that this bug is a duplicate of bug 111901. Did you even read the other bug?

Currently, this bug is set to depend on bug 113430. That bug is a meta bug, however. I think this bug should be set to block bug 113430. Thus, making the change accordingly.

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