Closed Bug 271683 Opened 20 years ago Closed 20 years ago

Firefox trying to load favicon.ico but should not to.

Categories

(Firefox :: Address Bar, defect)

Product:
Firefox
Component:
Address Bar
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 175909

People

(Reporter: paul_y, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0

Firefox somewhat trying to load "/favicon.ico" every time the web-page requested
from server. AFAIK, favicon should be loaded only if the web-page contains in
HEAD section something like

<link rel="SHORTCUT ICON" href="/favicon.ico">

But firefox always do this and thus generates an error in web-server's error.log

Reproducible: Always
Steps to Reproduce:
1. Open any page without favicon from any server, where you have shell access
2. Look in apache's logs/error.log

Actual Results:  
In apache's error.log I see:

[Thu Nov 25 12:22:59 2004] [error] [client 192.168.0.110] File does not exist:
C:/htdocs/favicon.ico

Expected Results:  
Firefox should try to load /favicon.ico if it's described in <HEAD> of page and
should not to load if not described.
That was a design decission, to be compatible with Micro$oft Exploder.

*** This bug has been marked as a duplicate of 175909 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
I may be out of order, but this looks more like a dup of Bug 260500
(Browser requests favicon.ico on every page view).

See also Bug 118548, Bug 116801

Webmasters are pointing out that Firefox makes repeated otiose requests
for /favicon.ico, and I suspect see compatibility with one particular
legacy browser as a lesser issue. The sad thing is that end users (who
by and large do want favicons) probably don't get any benefit from the 
aggressive search.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.