No, that wasn't what I was looking for. I'm concerned about the security
risk of exposing content of files that we didn't intend to. The .bak file
might be a web.config.bak that contains some sensitive info; I don't want
users to have access to it.


"David Wang" <w3.4you@gmail.com> wrote in message
news:1193981533.581025.25860@q3g2000prf.googlegroups.com...
> On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote: 
>
>
>
> 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
> //
>

[ Post a follow-up to this message ]