> I just noticed that IIS5 considers directories that end in an extension
> which is also used for commands (.com or .exe) to be executables and
> not directories. This means you can't name a directory "123.com",
> which kinda sucks as I like naming my directories after the domain
> name. Does MS have a reason for this or is it just another case of
> them writing bad software?
IIRC the combination of IISLockDown and execute permissions
causes such problems. That's why I lock down IIS with my own
scripts and don't use IISLockDown or URLScan.
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
