• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

XF 1.3 favicon.ico 404 not found error

Mike

XenForo developer
Staff member
#2
I saw a 404 once in one of my actual requests related to the favicon, but it was coming from Google's servers.

It could be related to this line that you have added:
Code:
<link rel="shortcut icon" href="favicon.ico" pagespeed_lsc_url="https://www.phcorner.net/favicon.ico"/>
The request appearing on those tests would be indicative of how a browser would treat that URL if it didn't handle the base tag. That could be a legitimate error, but it's not evident what is causing the request as I can't see any sort of stack trace and I can't reproduce the issue with my own browser. Alternatively, it could be a quirk with the actual test bed.
 

Carlos

Well-known member
#3
I hope the OP knows that he can add favicon.ico to the root and be done with it (ahem; nothing else to do).
 

Mike

XenForo developer
Staff member
#4
That's unrelated to the issue being reported... (It already exists and that's not where the error is coming from.)
 

Carlos

Well-known member
#5
That's unrelated to the issue being reported... (It already exists and that's not where the error is coming from.)
I read it again, then again, and I was going like "Ohh.. THAT!"

It's like... google's interfering with the favicon code. *embarrassed look* :oops:
 

RoldanLT

Well-known member
#6
It could be related to this line that you have added:
Code:
<link rel="shortcut icon" href="favicon.ico" pagespeed_lsc_url="https://www.phcorner.net/favicon.ico"/>
That code is modified automatically by ngx_pagespeed module.
xenmediagallery.com site one of the URL I tested still has an issue of favicon.ico not found but I know they are not using ngx_pagespeed.
@Chris D is this something to do with Live Update addon?
 

Mike

XenForo developer
Staff member
#10
That code is modified automatically by ngx_pagespeed module.
I wasn't referring to the modification from pagespeed. You're pulling "favicon.ico" and relying on the <base> tag to do the work for the browser to pull it from the correct location in the route (XF uses this approach in general). I'm not saying it's inherently wrong, but there may be clients that don't understand it and JS needs to be explicitly modified to handle things like <base> tags. Using "/favicon.ico" should eliminate that variable.