The -T is "too late" because, unlike Apache, IIS (and PWS) execute CGI scripts by first looking up the binding for .cgi in its internal scriptmap. The command in the scriptmap is then executed, and the name of the script is passed as an argument. Typically, the scriptmap for .cgi will be   .cgi     "c:\perl\bin\perl.exe %s %s" So when the CGI script is executed, there's no -T on the command line. The -T in the script header is "too late". One way to fix this is to edit the IIS scriptmap to change the binding to   .cgi     "c:\perl\bin\perl.exe -T %s %s" This means that all CGI scripts will run with taint checking. Since that might break other scripts, you might instead consider adding a scriptmap entry   .cgt     "c:\perl\bin\perl.exe -T %s %s"

Oh. i don't have control of this server - it's with an isp. they are so lame. i guess i have to call them and wait on hold for half an hour and see if they can fix it.

neophyte Niederrhein.pm

Unfortunately, I'm having the same exact problem with CGI programs on both my laptop and my computer. I've added the -T to the registry like everyone says, but I still get the error message. Yes, I restarted my computer (and by extension, the service) after the changes were made.

I'm running Win98 with PWS on both machines, so if anyone has any suggestions, I'm all for it. As a side note, running the program from the command line with the -T works just fine. For now, I'm making do without by incrementally uploading my programs to my webhost so I can test via CGI with taint turned on, but it's a huge pain.

Update: Due to several complaints, removed signature

Sarah

Did you remember to take the -T out of the #! line after you added it to the registry scriptmap?

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

what do you mean by add it to the registry?