You are reading a single comment by @arrowplum and its replies.
Click here to read the full conversation.
-
yeah that is kind of what I figured. It makes sense, but then why doesn't that /favicon.ico point to our spok?
I was a little confused why the net panel doesn't show the request for the file (even after deleting all of the favicons) but I guess developer tools Network panel != a packet sniffer.
Anyways, thanks.
arrowplum-
why doesn't that /favicon.ico point to our spok
Why introduce another database query on every static file request for favicon.ico when older browsers will honour the yet issue the request for favicon.ico regardless (does it concurrently).
Answer: performance.
Is it really necessary to have the right favicon when you're viewing source?
Velocio
Because if you're not viewing the HTML page which declares it's own favicon using the link element:
<link rel="shortcut icon" href="https://lfgss.microcosm.app/api/v1/files/3967bb6b279adca3d4b8a174c1021f3d642c32fc.png"/>Then what the browser is going to do is look for:
https://www.lfgss.com/favicon.icoAnd that redirects to:
https://www.lfgss.com/static/img/favico.pngWhich is the default favicon for sites that haven't declared a custom one.
Viewing source isn't viewing a web page, it's viewing a text file... and as such, the browser uses the default path, and default favicon at that time.