Hi guys.
If it’s not a bug - why I needed to on ‘force https’ in order to have favicon work?
AI-generated summary
A user, lejeczek, reported an issue with their favicon not appearing unless they enabled the ‘force https’ setting, despite already using the HTTPS protocol on their web server. pfaffman noted that HTTPS has been required for some years and that it’s likely not the only thing that’s broken without it. Falco mentioned that most installations following the official guide have ‘force_https’ enabled by default, making this issue rare. pfaffman suggested that ‘force_https’ should be enabled by default to prevent similar issues in the future.
I’m pretty sure that https has been required for some years now. I think that favicons are not the only thing that’s broken without https.
I was being specific - or perhaps not enough? - 'force https’ in ‘settings’ I had to enable for favicon to appear, even with https protocol already set & used on the web server end.
Worth mentioning that every install following our official install guide ends up with force_https enabled out of the box, making problems like this very rare and limited to custom installs.
Maybe it should just be enabled by default? Maybe it’s better to just be broken if they somehow try not to use https.