Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answeredpreviously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.

[EDIT/UPDATE FOR EXPLICIT ANSWER]
Move or redirect requests for your icons to the root folder so that the following resolve:

<link rel="shortcut icon" href="/favicon.ico">
<link rel="apple-touch-icon image_src" href="/apple-touch-icon-precomposed.png">

Then add/provision for the other requests as outlined here.

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.

[EDIT/UPDATE FOR EXPLICIT ANSWER]
Move or redirect requests for your icons to the root folder so that the following resolve:

<link rel="shortcut icon" href="/favicon.ico">
<link rel="apple-touch-icon image_src" href="/apple-touch-icon-precomposed.png">

Then add/provision for the other requests as outlined here.

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.

[EDIT/UPDATE FOR EXPLICIT ANSWER]
Move or redirect requests for your icons to the root folder so that the following resolve:

<link rel="shortcut icon" href="/favicon.ico">
<link rel="apple-touch-icon image_src" href="/apple-touch-icon-precomposed.png">

Then add/provision for the other requests as outlined here.

update with specific answer to address issue, rather than explain it.
Source Link
Mike Hudson
  • 5.5k
  • 24
  • 30

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.

[EDIT/UPDATE FOR EXPLICIT ANSWER]
Move or redirect requests for your icons to the root folder so that the following resolve:

<link rel="shortcut icon" href="/favicon.ico">
<link rel="apple-touch-icon image_src" href="/apple-touch-icon-precomposed.png">

Then add/provision for the other requests as outlined here.

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.

[EDIT/UPDATE FOR EXPLICIT ANSWER]
Move or redirect requests for your icons to the root folder so that the following resolve:

<link rel="shortcut icon" href="/favicon.ico">
<link rel="apple-touch-icon image_src" href="/apple-touch-icon-precomposed.png">

Then add/provision for the other requests as outlined here.

Source Link
Mike Hudson
  • 5.5k
  • 24
  • 30

It would be worth looking at the user-agent values for those requests causing the 404's. As previously asked/answered, browsers will normally follow the <link> location before any default request is made against the root folder of the site.

The error logs you are seeing are due to your file locations being in other directories. Most browsers will find them as they've parsed your HTML and located the appropriate <link> declaration, but others may not.