in reply to what instead of #!/usr/bin/perl
If you decide to go with Apache for Windows, you can read this link for step-by-step instructions on how to set it up.
I haven't used Personal Web Server, that I recall, but it may be a case of associating the .cgi extension with the Perl executable. Personally, I don't like that as it typically requires editing the registry to manually add the -T switch to turn on taint checking. Otherwise, if the shebang line (#!/usr/bin/perl) is the problem, change it to the path of the Perl executable. It will then resemble something like the following:
#!C:\perl\bin\perl.exe -wT
The -wT, strictly speaking, isn't necessary, but the warnings are helpful when developing your code and the -T switch is essential when doing Web programming as it turns on taint checking. See perlsec for details.
Last comment: if you are getting internal server errors, what do your Web server logs say? Find them and they'll probably tell you exactly what the problem is.
Cheers,
Ovid
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re (tilly) 2: what instead of #!/usr/bin/perl
by tilly (Archbishop) on Apr 09, 2001 at 20:28 UTC |