in reply to Perl hosting setup and taint check.

The problem you are having is that in Windows you need to make the file association. If you are using a ".cgi" extension on your files, you will need to change the association for that file. When you change the association, add the -T switch to the end of the perl command line.

TStanley
--------
Never underestimate the power of very stupid people in large groups -- Anonymous
  • Comment on Re: Perl hosting setup and taint check.

Replies are listed 'Best First'.
Re: Re: Perl hosting setup and taint check.
by tommyw (Hermit) on Aug 12, 2002 at 11:45 UTC
Re: Re: Perl hosting setup and taint check.
by Nemp (Pilgrim) on Aug 12, 2002 at 11:52 UTC

    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

Re: Re: Perl hosting setup and taint check.
by Anonymous Monk on Aug 12, 2002 at 12:31 UTC
    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.

      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