IIS error with .com in virtual directory name

External Since: Aug 04, 2004 Posts: 2

Hi,
I have a client application that loads a file under (webroot)/domainname/file.txt. This works fine when I create the virtual directory & call it e.g. microsoft.co.uk, but as soon as I use .com (e.g. microsoft.com/file.txt), IIS rejects the client request with a 403.1 error - execute access forbidden. IIS seems to think that the virtual directory name is the end file & therefore thinks I'm trying to run executable code:-(

I've tried changing the permissions to allow executable on the virtual directory & files in it but no luck.
A colleague of mine has managed to make it work only once as follows:-

Create a Virtual Directory peter.microsoft.com with read only access (no browsing, no executing allowed) and mapped it to a local folder, create a subdirectory and put a file in. http://localhost/peter.microsoft.com/files/test.txt

Of course it didn't work.
Do the following:
- In Internet Services Manager right click on the virtual directory, select browse, you're not allowed to .....
- close the browser window
- In Internet Services Manager double click on the virtual directory, double click on the sub-folder, right click on the file and select browse, the file is shown
- now you can see the file but if you try from other clients or refresh the browser you get the 403.1 error again.

This is no solution, but may be a direction to look at: Does anyone know of a way of configuring IIS or registry tweak, or MS patch etc to stop IIS from assuming that .com in the virtual directory name (not the file since its a .txt!) is an executable??

I am running IIS 5 win2K server SP4. My colleague reproduced this on IIS 5, but got it to work fine on IIS6, and I had no problems on an Apache server either.

External Since: Apr 12, 2004 Posts: 214

Dave A wrote:

> Hi,
> I have a client application that loads a file under (webroot)/domainname/file.txt. This works fine when I create the virtual directory & call it e.g. microsoft.co.uk, but as soon as I use .com (e.g. microsoft.com/file.txt), IIS rejects the client request with a 403.1 error - execute access forbidden. IIS seems to think that the virtual directory name is the end file & therefore thinks I'm trying to run executable code:-(
>
> I've tried changing the permissions to allow executable on the virtual directory & files in it but no luck.
> A colleague of mine has managed to make it work only once as follows:-
>
<font color=purple> > Create a Virtual Directory peter.microsoft.com with read only access (no browsing, no executing allowed) and mapped it to a local folder, create a subdirectory and put a file in. <a style='text-decoration: underline;' href="http://localhost/peter.microsoft.com/files/test.txt</font" target="_blank">http://localhost/peter.microsoft.com/files/test.txt</font</a>>
>
> Of course it didn't work.
> Do the following:
> - In Internet Services Manager right click on the virtual directory, select browse, you're not allowed to .....
> - close the browser window
> - In Internet Services Manager double click on the virtual directory, double click on the sub-folder, right click on the file and select browse, the file is shown
> - now you can see the file but if you try from other clients or refresh the browser you get the 403.1 error again.
>
> This is no solution, but may be a direction to look at: Does anyone know of a way of configuring IIS or registry tweak, or MS patch etc to stop IIS from assuming that .com in the virtual directory name (not the file since its a .txt!) is an executable??
>
> I am running IIS 5 win2K server SP4. My colleague reproduced this on IIS 5, but got it to work fine on IIS6, and I had no problems on an Apache server either.
>
>
>
>

Sorry, this is behavior by design:

<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;275601" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;275601</a>