Re: Re: Re: Re: Re: Re: Re: 500 Internal Server Error

IIS uses the shebang line, and thus uses PerlIS. Apache reads the httpd.conf and thus uses the registry entry and ignores the shebang line. PerlIS runs ALOT faster with IIS. If you care to follow the link I posted, you'll understand why this is. PerlIS was written by ActiveState to better integrate Perl with IIS.

Please note the OP mention they were using Windows NOT Unix. What I suggested was applicable to their situation.

--
Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/

Comment on Re: Re: Re: Re: Re: Re: Re: 500 Internal Server Error - Using ActiveState perl

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Re: Re: Re: 500 Internal Server Error - Using ActiveState perl by Anonymous Monk on Jan 10, 2004 at 11:31 UTC
Apache reads the httpd.conf and thus uses the registry entry and ignores the shebang line. Maybe your copy of apache, but standard apache doesn't perform any such magic. mod_perl maybe, but not apache.	[reply]
Re: Re: Re: Re: Re: Re: Re: Re: Re: 500 Internal Server Error - Using ActiveState perl by barbie (Deacon) on Jan 11, 2004 at 01:46 UTC
Ahem, may I direct you to .... a description from an online manual This directive is used to control how Apache finds the interpreter used to run CGI scripts. The default technique is to use the interpreter pointed to by the #! line in the script. Setting ScriptInterpreterSource registry will cause the Windows Registry to be searched using the script file extension (e.g., .pl) as a search key. That's standard Apache on Win32 :) -- Barbie \| Birmingham Perl Mongers \| http://birmingham.pm.org/	[reply]