Yes, I got that the first time. However using the file manager is quite awkward when giving the customer the option of having multiple favicons to choose from. Not to mention the fact that this doesn't address the skin designer's needs whatsoever. And by skin designer I mean anyone who designs a skin. Consider that the designer may be a company employee, or a web designer working on a single solution for a specific client, not just a "commercial" skin designer.

It is my first position that favicons are part of a web site, and therefore should be controllable via the Site Settings page. Whether or not the skin paradigm is used to facilitate management tasks or not is secondary. (Again, my apologies for co-opting this thread.)

BTW, I was wrong about favicons location being limited by IIS. It's actually a combination of browser behavior and/or meta tags (for those who may not have already known).

I was originally thinking to implement this with asp.net code by mapping the .ico extension, etc.., but if it was just part of the skin subsystem then it would be so easy (with no IIS config required) to just write out a simple..

<link rel="shortcut icon" href="http://www.yoursite.com/Portals/_default/Skins/yourskin/favicon.ico" />

..for wherever the favicon will be sourced from.. searching in the current skin, portal root then finally the host root.