Why do you not recommend keeping all those icon files in separate directory as an alternative? It makes things a lot of cleaner without all those junk files (browser-sth-for ms-sth-ie.xml etc.) inside root directory (btw. the number of those files will grow every year, I guess). Besides what if you have many www roots for many vhosts and want to share the same icon? Symlinks aren't the option for someones. Couldn't you just add a small piece of config (as a hint at least) to alias /favicon.ico to lets say /static/favicon.ico (and for browser-sth-for ms-sth-ie.xml as well; that should be enough; Apple allows and respects custom icons declared in html) for Nginx and/or Apache, as a more advanced setup, and not "not recommended"?.
Why do you not recommend keeping all those icon files in separate directory as an alternative? It makes things a lot of cleaner without all those junk files (browser-sth-for ms-sth-ie.xml etc.) inside root directory (btw. the number of those files will grow every year, I guess). Besides what if you have many www roots for many vhosts and want to share the same icon? Symlinks aren't the option for someones. Couldn't you just add a small piece of config (as a hint at least) to alias
/favicon.ico
to lets say/static/favicon.ico
(and for browser-sth-for ms-sth-ie.xml as well; that should be enough; Apple allows and respects custom icons declared in html) for Nginx and/or Apache, as a more advanced setup, and not "not recommended"?.