Running scripts from directories with a "." in the directory name.

I am still learning about using IIS once again in my career. Anyway we have been working on migrating a web site from a BSD server to a IIS 5.0 server on Win2k. I copied over the content and got Perl installed and working and the site was mostly working. Several weeks later we have came back and turned up the site on the new server. This application that uses perl was working before but now it is not.

I have created a test.pl script and it is located at wwwroot\'website'\cgi-bin\we3.1\test.pl. The test will not work and all I get is a 'This oage can not be found' 404 message. I did some testing with various settings but finally copied over the content and it will work if the final directory is 'we31' and not 'we3.1' I think tightening the front page security or some other setting has broke this. Does anyone have any ideas so I dont have to edit and update all the scripts pointing into this directory?

Thanks,
Greg

jeff
Thu Jul 15 16:30:38 CDT 2004

On Thu, 15 Jul 2004 12:37:01 -0700, "GregP"
<GregP@discussions.microsoft.com> wrote:

>I am still learning about using IIS once again in my career. Anyway we have been working on migrating a web site from a BSD server to a IIS 5.0 server on Win2k. I copied over the content and got Perl installed and working and the site was mostly working. Several weeks later we have came back and turned up the site on the new server. This application that uses perl was working before but now it is not.
>
>I have created a test.pl script and it is located at wwwroot\'website'\cgi-bin\we3.1\test.pl. The test will not work and all I get is a 'This oage can not be found' 404 message. I did some testing with various settings but finally copied over the content and it will work if the final directory is 'we31' and not 'we3.1' I think tightening the front page security or some other setting has broke this. Does anyone have any ideas so I dont have to edit and update all the scripts pointing into this directory?

1) Never use reserved Windows names for folders
(\website\domain.com\filename.pl for example)

2) Never use a dot in the path if you can help it.

3) When you have to ignore #2, use the AllowDotInPath setting in your
URLScan.ini file so this request doesn't get blocked.

4) When you have a problem, check the IIS log files for the actual
request, in this case it probably shows a "Rejected-by-URLScan" entry.

5) The URLScan.ini file has this commented in it.

6) URLScan notes include:

http://microsoft.com/technet/treeview/default.asp?url=/technet/security/tools/tools/urlscan.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;318290
http://support.microsoft.com/default.aspx?scid=kb;en-us;307976
http://support.microsoft.com/default.aspx?scid=kb;en-us;817807
http://support.microsoft.com/default.aspx?scid=kb;en-us;325864

7) We forgive you having run "that other operating system" in error
now that you switched to Windows and IIS. :)

Oh yeah, by the way, this is often caused by URLScan rejecting the
request...

Jeff

GregP
Thu Jul 15 19:41:01 CDT 2004

Yea I just learned all about the IIS Lockdown Tool and URL Scan. Got them all updated after finding this in the log. I will try and allow it or change the directory and the scripting. Thanks for the great answer!

I had ran the Baseline tool and then IIS Lockdown several weeks back after getting it to work and it sat for a while so that was the problem indeed.

Greg


"Jeff Cochran" wrote:

> On Thu, 15 Jul 2004 12:37:01 -0700, "GregP"
> <GregP@discussions.microsoft.com> wrote:
>
> >I am still learning about using IIS once again in my career. Anyway we have been working on migrating a web site from a BSD server to a IIS 5.0 server on Win2k. I copied over the content and got Perl installed and working and the site was mostly working. Several weeks later we have came back and turned up the site on the new server. This application that uses perl was working before but now it is not.
> >
> >I have created a test.pl script and it is located at wwwroot\'website'\cgi-bin\we3.1\test.pl. The test will not work and all I get is a 'This oage can not be found' 404 message. I did some testing with various settings but finally copied over the content and it will work if the final directory is 'we31' and not 'we3.1' I think tightening the front page security or some other setting has broke this. Does anyone have any ideas so I dont have to edit and update all the scripts pointing into this directory?
>
> 1) Never use reserved Windows names for folders
> (\website\domain.com\filename.pl for example)
>
> 2) Never use a dot in the path if you can help it.
>
> 3) When you have to ignore #2, use the AllowDotInPath setting in your
> URLScan.ini file so this request doesn't get blocked.
>
> 4) When you have a problem, check the IIS log files for the actual
> request, in this case it probably shows a "Rejected-by-URLScan" entry.
>
> 5) The URLScan.ini file has this commented in it.
>
> 6) URLScan notes include:
>
> http://microsoft.com/technet/treeview/default.asp?url=/technet/security/tools/tools/urlscan.asp
> http://support.microsoft.com/default.aspx?scid=kb;en-us;318290
> http://support.microsoft.com/default.aspx?scid=kb;en-us;307976
> http://support.microsoft.com/default.aspx?scid=kb;en-us;817807
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325864
>
> 7) We forgive you having run "that other operating system" in error
> now that you switched to Windows and IIS. :)
>
> Oh yeah, by the way, this is often caused by URLScan rejecting the
> request...
>
> Jeff
>

John
Sat Jul 17 13:32:46 CDT 2004

On Thu, 15 Jul 2004 12:37:01 -0700, GregP wrote:
>=A0I am still learning about using IIS once again in my career. Anyway
>=A0we have been working on migrating a web site from a BSD server to a
>=A0IIS 5.0 server on Win2k. =A0I copied over the content and got Perl
>=A0installed and working and the site was mostly working. =A0Several
>=A0weeks later we have came back and turned up the site on the new
>=A0server. =A0This application that uses perl was working before but now
>=A0it is not.
>
>
>=A0I have created a test.pl script and it is located at
>=A0wwwroot\'website'\cgi-bin\we3.1\test.pl. =A0The test will not work
>=A0and all I get is a 'This oage can not be found' 404 message. =A0I did
>=A0some testing with various settings but finally copied over the
>=A0content and it will work if the final directory is 'we31' and not
>=A0'we3.1' =A0I think tightening the front page security or some other
>=A0setting has broke this. =A0Does anyone have any ideas so I dont have
>=A0to edit and update all the scripts pointing into this directory?
>
>
>=A0Thanks,
>=A0Greg

You will run into other quirky problems using dots in the folder name. Take=
them out.

John Cesta

---------------------------------
The CPU Checker - Maximize Server Uptime
LogFileManager - The only IIS Logfile Management Tool
DomainReportIt PRO - Helps Convert IIS Installs
http://www.serverautomationtools.com