If that doesn't resolve the issue, you many need to use the Internet Service Manager to edit the scriptmap.

Yes, taking the -T out of the #! line will allow the program to run, but unfortunately, it also doesn't taint check.

I know that sounds really arrogant, but I tested this out. I created a tiny little file that purposely causes taint to scream:

#!perl -wT
use strict;

my $bad_stuff = $ENV{HOME};
system($bad_stuff);
[download]

I'm probably rehashing old news, but my testing shows that taint will puke over this whether or not the -T is in the #! line as long as perl is called with -T. But if I run it in the browser without the -T in the #! line, taint doesn't make a peep. This is all while the -T is still in the registry. But I'm probably misunderstanding the situation...

Update: Due to several complaints, removed signature

Sarah

I assume you've given the script a .cgi extension, and that you've located the W3SVC\Parameters\scriptmap in the registry, and have added -T to the value for the .cgi key, and that you've stopped and restarted IIS (or rebooted, for good measure).

If all this is the case, then you should see -T puking on your script when you invoke it through the browser.

I get "Too late for -T" when I also have -T in the #! line, but this may be Perl version-dependent behavior (I'm pretty far out of date on one box. This is probably a good excuse to upgrade.)

I solved the problem and have no experience in Perl or IIS (I guess now I have a little) All you have to do is this: Relates to IIS 5 or higher using ActivePerl 5.x for Win32 using ISAPI. Go into the properties of CGI virtual directory.. Click "Configuration" button on the Virtual Direcotry tab Click on your .pl extension and click edit Edit the line to reflect C:\perl\bin\perl.exe -T "%s" %s Apply changes.

what do you mean by add it to the registry?

I probably should have said "after you added it to the scriptmap."

There are two ways to edit the scriptmap. The common one is to use one of the registry editing tools (e.g., regedit) and then to restart IIS (and reboot if you're on Win98!)

The less common way is to use the Internet Service Manager, which makes you jump through five hoops to find where to access to the scriptmap.