| [reply] |
I'm using a ".pl" extension on my files. The webhost I am using shares access to the Perl interpreter so I don't think they will change the command line for when Perl scripts are invoked just for me :(. (I'll try though!!)
Is there anything I can tell my hosting company to do in regards to their Perl interpreter to allow me to use taint checking?
Thanks, Neil
| [reply] |
I copied your script exactly, and it ran fine under Apache on Red Hat 7.3 Linux. If the webserver is on a Windows 2000 platform, I seriously doubt the location of "perl" is "/usr/bin/perl" like you specified in the top #! line - I would expect to see something starting with "c:" with backslashes like "c:\path\to\perl".
HTH. | [reply] |
Sorry for any possible confusion, that was left in since I checked the script on my linux box at home. Saying that, I was under the impression that the location of Perl specified in the #! line didn't affect running at all under Windows (except for the modifiers after like -w etc.) Am I incorrect in this assumption?
Many thanks, Neil
| [reply] |