favicon.ico and LINK element

  • Thread starter Thread starter =?iso-8859-1?B?RnJhbudvaXM=?=
  • Start date Start date
?

=?iso-8859-1?B?RnJhbudvaXM=?=

Hi,

I followed the favicon instructions at:

http://msdn.microsoft.com/library/default.asp?url=/workshop/Author/dhtml/howto/ShortcutIcon.asp


Firefox does retrieve the icon in the particular folder where I dropped
it. IE6 does not.

Using Ethereal, I notice Firefox sends a proper GET to retrieve the
icon. IE6 does not. No request at all relative to the icon were made.

That makes me think IE chokes on the following lines, included in the
HEAD section:

<LINK REL="ICON" HREF="images/favicon.ico">
<LINK REL="SHORTCUT ICON" HREF="images/favicon.ico">

It either can't read them or does not process them (even if I drop the
link on the link bar, which, for IE, is the cue to send a GET request).

Even with an absolute path, no requests whatsoever.

If I remove the above lines, IE sends a GET /favicon.ico, but Firefox
doesn't. Firefox needs the LINK.

Interesting catch-22 situation. I did workaround the problem by
removing the lines and, using javascript, append on window.onload the
LINK lines to the HEAD section. IE did not see them, issued a GET
request for /favicon.ico, and Firefox sent a GET following the absolute
or relative path to the favicon.

My question: does anyone know why IE6 doesn't send a GET when there's a
"shortcut icon" LINK?

Thanks in advance for any info.

F.
 
François said:
Hi,

I followed the favicon instructions at:

http://msdn.microsoft.com/library/default.asp?url=/workshop/Author/dhtml/howto/ShortcutIcon.asp


Firefox does retrieve the icon in the particular folder where I dropped
it. IE6 does not.

Using Ethereal, I notice Firefox sends a proper GET to retrieve the
icon. IE6 does not. No request at all relative to the icon were made.

That makes me think IE chokes on the following lines, included in the
HEAD section:

<LINK REL="ICON" HREF="images/favicon.ico">
<LINK REL="SHORTCUT ICON" HREF="images/favicon.ico">

It either can't read them or does not process them (even if I drop the
link on the link bar, which, for IE, is the cue to send a GET request).

Even with an absolute path, no requests whatsoever.

If I remove the above lines, IE sends a GET /favicon.ico, but Firefox
doesn't. Firefox needs the LINK.

Interesting catch-22 situation. I did workaround the problem by
removing the lines and, using javascript, append on window.onload the
LINK lines to the HEAD section. IE did not see them, issued a GET
request for /favicon.ico, and Firefox sent a GET following the absolute
or relative path to the favicon.

My question: does anyone know why IE6 doesn't send a GET when there's a
"shortcut icon" LINK?

Thanks in advance for any info.
Click to expand...

"The only way a shortcut icon appears on a user's Favorites menu and Address
bar is if the user chooses to add your page as a favorite." AFAIK, this only
applies to IE and I don't see from above that you did this. Try adding the
link to favorites and see if that works.

Tom
 
"The only way a shortcut icon appears on a user's Favorites menu and Address
bar is if the user chooses to add your page as a favorite." AFAIK, this only
applies to IE and I don't see from above that you did this. Try adding the
link to favorites and see if that works.

Tom
Click to expand...

Thanks Tom,

Did so: no request was made to the server for the ico, even when
putting the link in the favorites, or the "link bar", or on the
desktop, etc.

I posted this because no one mentionned the absent GET request with IE.

I was wondering if anyone had a similar experience.

Regards,

François
 
François said:
Thanks Tom,

Did so: no request was made to the server for the ico, even when
putting the link in the favorites, or the "link bar", or on the
desktop, etc.

I posted this because no one mentionned the absent GET request with IE.

I was wondering if anyone had a similar experience.
Click to expand...

It works for me. Are you using the "Add to favorites..." from IE's menu?
That is the only way IE will fetch the favicon. If that is what you are
doing then your IE appears to be broken.

Tom
 
Back
Top