I'd like to set up IIS so that if give a directory a particular name, then IIS will not serve the contents of that directory. So for example, let's say the special name is "secure"

I have my home directory. I can put an html file in the directory and view it on the web. If I create a directory named /secure/ then IIS will not serve any pages in that directory.

Here is what I DONT want to do:

I do not want to have to set security permissions on this directory. I have thousands of users. I would be on the phone all day setting and unsetting directories.

urlscan will check a file extension and can block the file based on that - meaning, if you rename a file to *.htc then IIS will instantly stop serving it. You don't have to set any security permissions on the file. I'm looking for a solution similar to that, except for directories.

I know there are a lot of smart people here, so I thought I would ask.

I initially read that as "IIGS", and was going to comment that my IIGS is currently sitting in the basement and unable to boot, but, since you're not discussing an archaic computer, I'll bow out of the thread now.

LOL, that was my first thought also. As for my IIGS, I sold it about 13 years ago. So I can't tell you where it's at.

__________________
Some try to tell me, thoughts they cannot defend,... - Moody Blues.

I'm not positive that this will work, but setting the directory name to $secure, or anything that starts with $ (maybe it's $_) will make it a hidden folder and therefore unavailable. At least if I remember correctly. Oh, and this is for a windows system. In theory, someone could still open it, but they would have type in the address manually and if they don't knoe the name, that will be tough.

__________________
I'm not evil.
An evil person would do the things I think up.

ok. I'll give it a try. Thanks!

I'm not clear on the goal... But it sounds like you just want to use the ISS properties on the directory, and set "Execute Permisions" to None, and turn off directory browsing.

__________________
Numbers are not case sensitive. (me)

I'm pretty sure search engines will pick it up.

__________________
In Fallout 3, 'happiness' is a warm junkyard dog and a loaded gun. It's mostly the loaded gun.
- Moose's one-line review.

"your going to regret that one. You are now a colonoscope...
- Chrissy, corrupting PraedSt's wish.

What I did with my linux system was somewhat the opposite. The users home directory was not visible to the web server. However, in each home directory was a symbolic link, created by a modded adduser script, which pointed to the user's directory within the web server's accessible space on a different drive.

That meant that a user ftping onto the server would have to change directories into their web space in order to upload their files. If they didn't want the files to be visible, they could upload the files to their normal account space.

It's always better to globally deny then explicitly grant than to globally grant and explicitly deny.

It'll make tracking their quotas a little bit harder, but it wasn't an issue for me. I wasn't worried about drive space. Only bandwidth.

__________________
In Fallout 3, 'happiness' is a warm junkyard dog and a loaded gun. It's mostly the loaded gun.
- Moose's one-line review.

"your going to regret that one. You are now a colonoscope...
- Chrissy, corrupting PraedSt's wish.