You need to sign in to do that
Don't have an account?
Sites favicon implementation does not work unless using custom domain configuration
Modern browsers are expecting the favicon to be in the root of the website. In sites, it's implemented in the root of the "site" app folder, rather than the root of the <company>.force.com folder, which is the stock Salesforce favicon. I'm presuming this was either an oversight, or based on the assumption that no one would want both favicon support and be required to use the *.force.com hostname.
The only way favicon support will work in this implementation is if:
- You are using a custom domain
- Due to 1, you are also not using SSL
Please allow for the favicon support to be set at a company level instead of on a per-site level. The use case for having separate favicons in the same business/company must be much smaller than the use case for needing it on separate sites for the same company (ie,SF org).
Examples
https://logmein.secure.force.com/favicon.ico = SF icon
https://logmein.secure.force.com/support/favicon.ico = our configured icon
I didn't bother posting this to the ideas site because apparently the use case for requiring SSL on all sites traffic is so small. I figured posting to Ideas would be a waste of time.
Either way, it's a pretty large hole in the feature, and in the short term, it definitely needs to be documented. Troubleshooting this was a pain due to the "it will take 24 hours to see your change due to caching" comment, which is also not completely accurate. Instructions for implementing this and verifying it as successful merely involve visiting the URL for the favicon directly, so I don't see why that couldn't be added to the documentation as well.
All Answers
You don't need your icon in the root path if you add an additional html tag to your VF Page :