I placed a favicon.ico in my skin package, but upon uploading and installing I find that it is stripped out because .ico is not an allowed file extension. I know I can easily change the site to allow this, but by default it is not allowed.. and anyway I have a feeling that storing the favicon in the skin folder location will work anyway..

So yes I do know that each page can have a different skin set, so in this case, by my logic, then each skin package should be able to supply its own favicon. That sounds ok to me (no manual upload into portal root),  what do you think?

It could be done if asp.net handled the favicon.ico file, then programatically DNN could simply fetch the appropriate bits from the first available instance of the file, ie.  the skin, then the portal root, then the host root or dnn.ico for example.

Hi Sebastion, I think you missed the point of my post..
I know that you can set the host to allow .ico files (I even said that), but, storing the favicon in the skin folder does not have the desired affect. ie. it needs to be stored in the portal root.

So what I am saying/suggesting is, 'should' the favicon bits be sourced from the skin folder?
(this would require only a small amount of code to accomplish)

ie. should the favicon be part of the 'skin'.. just wondering what people think about that?

I always use the favicon to add an visual identifier for the web site, not for a single page or an assigned design, and AFAIK this is the idea behind the favicon. If you create a custom web design, the favicon might be part of it like the logo, but IMO it is not too difficult for a portal admin, to place it manually into the portal root.