IIS Server Security - Re: file extensions and IIS

This is Interesting: Free IT Magazines  
Home > Archive > IIS Server Security > November 2007 > Re: file extensions and IIS





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: file extensions and IIS
David Wang

2007-11-16, 1:39 pm

On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote:
> Hi,
>
> I'm wondering which file extensions are treated as "exposed" and which are
> "hidden" by the IIS? I was told that the .bak file is exposed so external
> users can actually browse and see content of files with .bak extension but I
> couldn't reproduce it. Thanks for your advice and pointers.




IIS does not treat file extensions as "hidden" or "exposed".

So, the behavior of .bak file that you describe does not exist, and I
don't really know what you are trying to reproduce.

What IIS *does* do is route all requests by file extension to be
"handled" (i.e. processed) by something. That something is called a
"handler", and the handler decides what to do with the resource.

It sounds like you want to make a directory browseable and .bak files
downloadable, which means you want to enable Directory Browsing for a
directory and set a MIME Type for the .bak extension to enable its
contents to be browsed and seen by a browsing user.

Please search for documentation on "Directory Browsing" and "MIME
Type" on how to accomplish them. If they are not what you want, please
describe further what behavior you want.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com