RE: os-windows/1919: Perl CGI Execution (with solution) (fwd)

[Marc Slemko <ma...@znep.com>]

The following reply was made to PR os-windows/1919; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: Apache bugs database <ap...@apache.org>
Cc:  Subject: RE: os-windows/1919: Perl CGI Execution (with solution) (fwd)
Date: Fri, 6 Mar 1998 23:16:16 -0700 (MST)

 ---------- Forwarded message ----------
 Date: Fri, 06 Mar 98 15:01:00 PST
 From: Adam Turoff <Ad...@smginc.com>
 To: marc <ma...@hyperreal.org>
 Subject: RE: os-windows/1919: Perl CGI Execution (with solution)
 
 
 > Synopsis: Perl CGI Execution (with solution)
 >
 > State-Changed-From-To: open-closed
 > State-Changed-By: marc
 > State-Changed-When: Fri Mar  6 11:34:48 PST 1998
 > State-Changed-Why:
 > Yes, that does work to allow portability without changes.
 > Note that the current tree and 1.3b3 (although not
 > 1.3b5) will properly execute perl.exe even if just
 > perl is named in the #! line, with the right directory of course.
 >
 > At some point, Apache will probably add the feature to allow
 > people to use registry associations, but that is on the todo
 > list.
 
 Thanks for the quick response.
 
 All things considered, taking advantage of the 1.3b3/1.3b5 behavior
 of loading /usr/bin/perl in the near term before Apache recognizes
 *.pl as a valid extension might be a better quick fix for some than
 using the more widely publicized solution of  #!c:/perl/bin/perl.exe.
 
 We've come up against this problem before since we're a dual
 system shop.  Normally NT ignores #! lines, and Unix doesn't
 care about .pl extensions.  Taking advantage of both is the easiest
 and most painless solution we found.
 
 Just thought I'd pass the idea around.  Glad to hear that the
 registry solution is in the hopper.
 
  -- Adam.