You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Bill Luebkert <db...@wgn.net> on 1999/04/14 00:50:43 UTC

config/4241: Need to be able to override shebang line to make CGI scripts more portable.

>Number:         4241
>Category:       config
>Synopsis:       Need to be able to override shebang line to make CGI scripts more portable.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Apr 13 17:10:01 PDT 1999
>Last-Modified:
>Originator:     dbe@wgn.net
>Organization:
apache
>Release:        1.3.6
>Environment:
All, especially Win32
>Description:
<pre>

In order to not have to modify each script when porting CGI scripts to different 
platforms, there ought to be a way to override the shebang line to specify where 
a given CGI app lies.

Proposed syntax in server config, virtual host, .htaccess:
    CGIOverride {<full-path-to-app>|off} <file-ext-list>
or
    ShebangOverride {<full-path-to-app>|off} <file-ext-list>

Eg:
CGIOverride c:/perl/bin/perl.exe .pl .cgi  # override shebang line on .pl and .cgi scripts
CGIOverride off .cgi                       # turn shebang override back off for this dir (.htaccess)

Possibly also:
CGIOverride c:/perl/bin/perl.exe form.pl   # override a single script (probably only used in .htaccess)

</pre>
>How-To-Repeat:

>Fix:
Possible changes to ap_execve.c, util_script.c, mod_cgi.c, etc. to implement, 
plus addition of syntax above.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]