Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

Archive: https://archive.today/iyv7Q

From the post:

>First up, why in the hell do you need to request the same link 12 times? No, scratch that, 15 times, since it does 3 more after getting the css and feed icon. Then it goes for the favicon, and what clown decided that the right way to request "/favicon.ico" is to prepend the base path to it? This cursed thing that Microsoft foisted upon us back in the 90s is supposed to be at the top level. It's not part of individual directories. That would be stupid.

Archive: https://archive.today/iyv7Q From the post: >>First up, why in the hell do you need to request the same link 12 times? No, scratch that, 15 times, since it does 3 more after getting the css and feed icon. Then it goes for the favicon, and what clown decided that the right way to request "/favicon.ico" is to prepend the base path to it? This cursed thing that Microsoft foisted upon us back in the 90s is supposed to be at the top level. It's not part of individual directories. That would be stupid.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (3).
[–] • 2 pts

It's easy to imagine how this happens. Browser is in charge of favicon access. Components request it for various purposes. When it doesn't get it, it keeps requesting every time, rather than noting that it's not there and waiting say a day before requesting again. Or icon is there but there's an error caching it locally so it requests every time.