cgi and mod_perl config question

2001-07-09 Thread Wayne Earl

A client's webserver appears to have both mod_perl and cgi configured for
a single machine. The httpd.conf file contains the following:

Files *.cgi
SetHandler perl-script
PerlHandler Apache::Registry
Options ExecCGI
/Files

A little later in the file, this is found:

AddHandler cgi-script .cgi

Is the handler first defined used (mod_perl), or is mod_perl ignored,
running the script as a standard cgi? Commenting out the cgi-script
handler seems to have no effect, both in apache footprint or webserver
performance, so I suspect that mod_perl is being used here.

Am I correct in assuming this?

This machine is running apache 1.3.20, with mod_perl 1.25 compiled
statically (not a DSO).
-- 
Wayne Earl [EMAIL PROTECTED]
gpg key fingerprint: 3CE4 0558 635E DADB 327C 73AB 11CA 9A6B B209 E8C5




Re: cgi and mod_perl config question

2001-07-09 Thread Stas Bekman

On Mon, 9 Jul 2001, Wayne Earl wrote:

 A client's webserver appears to have both mod_perl and cgi configured for
 a single machine. The httpd.conf file contains the following:

 Files *.cgi
 SetHandler perl-script
 PerlHandler Apache::Registry
 Options ExecCGI
 /Files

 A little later in the file, this is found:

 AddHandler cgi-script .cgi

 Is the handler first defined used (mod_perl), or is mod_perl ignored,
 running the script as a standard cgi? Commenting out the cgi-script
 handler seems to have no effect, both in apache footprint or webserver
 performance, so I suspect that mod_perl is being used here.

 Am I correct in assuming this?

Since you don't provide the whole file it's hard to tell, since according
to the manual the later setting should take over the previous setting:

QUOTE
AddHandler maps the filename extensions extension to the handler
handler-name. This mapping is added to any already in force,
overriding any mappings that already exist for the same extension. For
example, to activate CGI scripts with the file extension .cgi,
you might use:

AddHandler cgi-script .cgi

Once that has been put into your srm.conf or httpd.conf file, any file
containing the .cgi extension will be treated as a CGI program.
/QUOTE

but this should answer all your questions:
http://perl.apache.org/guide/install.html#How_can_I_tell_whether_mod_perl_
(skip the error log testing section)

 This machine is running apache 1.3.20, with mod_perl 1.25 compiled
 statically (not a DSO).
 --
 Wayne Earl [EMAIL PROTECTED]
 gpg key fingerprint: 3CE4 0558 635E DADB 327C 73AB 11CA 9A6B B209 E8C5




_
Stas Bekman  JAm_pH --   Just Another mod_perl Hacker
http://stason.org/   mod_perl Guide  http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]   http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/