Non-existent favicon.ico requested twice in a row in short time




10 years ago
7 years ago


(Reporter: The Reporter, Unassigned)


2.0 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-07-30])



10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20071025 Firefox/
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20071025 Firefox/

Firefox requests twice in a row in short time a favicon.ico file that does not exist. The server returns "HTTP 410 Gone". I didn't test HTTP 404.

Reproducible: Always

Steps to Reproduce:

Expected Results:  
Request the favicon.ico file only once. Not twice in a row in a short time, which wastes bandwidth both of the user and of the server, etc.

Comment 1

10 years ago
By "short time" I mean anything between 0.01 and several seconds.


10 years ago
Last Resolved: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 299031

Comment 3

10 years ago
This is not a duplicate of the bug 299031. The bug 299031 does not deal with re-requesting the favicon.ico file TWICE on a SINGLE page load. That bug deals with re-requesting the favicon.ico file on SUBSEQUENT page loads. This is about a single page being loaded and favicon.ico requested twice in near-zero time. 

Read what I wrote. It may apply to HTTP 404 (I haven't tested that). These bugs are not duplicate. 
Resolution: DUPLICATE → ---

Comment 4

10 years ago
You request a page widget.html:

Firefox does:
GET widget.html
GET favicon.ico
GET favicon.ico

All that within less than one second.

Comment 5

10 years ago
no : read bug 299031 comment 2. A 410 should be cached (point 2). And a favicon request might also be treated differently form a regular request (point 1).

Comment 6

10 years ago
First, I don't see HTTP 404 mentioned anywhere. This bug may affect 404 too.

Second, let me quote from the first post, the actual bug report, 299031.

"Our server returns 410 for the /favicon.ico file. Despite that Firefox keeps 
requesting the file while the user continues browsing other pages on the same 
site (e.g. and then"

Note the words "other pages on the same site".

This bug is about only a SINGLE PAGE request. That bug is about CACHING results between requesting MULTIPLE PAGES, possible minutes or hours between.


9 years ago
Duplicate of this bug: 443660
Duplicate of this bug: 468098
Easy-to-use steps to reproduce, no external server access or packet watching needed:

$ cd $srcdir
$ echo "var DEBUG = true;" > testing/mochitest/
$ cat testing/mochitest/server.js >> testing/mochitest/
$ mv testing/mochitest/server.js{.new,}
$ python $OBJDIR/_tests/testing/mochitest/ --test-path=q

...and watch the debug output for two /favicon.ico requests.
On my linux box, I ran 'python -m SimpleHTTPServer' and visited the site using Firefox 3.5b4pre Build 20090406050537 and Firefox requested the /favicon.ico twice.

MASTER - - [06/Apr/2009 20:44:25] "GET / HTTP/1.1" 200 -
MASTER - - [06/Apr/2009 20:44:25] code 404, message File not found
MASTER - - [06/Apr/2009 20:44:25] "GET /favicon.ico HTTP/1.1" 404 -
MASTER - - [06/Apr/2009 20:44:28] code 404, message File not found
MASTER - - [06/Apr/2009 20:44:28] "GET /favicon.ico HTTP/1.1" 404 -

Firefox has also filled up the error log on my Apache servers on normal internet sites where I'm too lazy to upload a favicon.ico.
This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 10 years ago7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.