Geoff and Stas, Thanks for your help so far. It's great to have such experts available such as
yourselves. And the humor is even good to ;--)--
;)
The $ENV{MOD_PER} is being returned now with the following syntax in the
httpd.conf file:
<Directory "/opt/famhistdev/fhdev1/bin">
Options Indexes FollowSymLinks MultiViews ExecCGI
AllowOverride AuthConfig
Order allow,deny
<Files "*">
# new
# cws: 3/13/04 Commented out SetHandler perl-script as don't need to
# have mod_perl 1.0-type behavior for now. See comment in Geoff's
# skeleton test suite that says to use perl-script if you want
# mod_perl 1.0 behavior.
# SetHandler perl-script
that's not so correct. perl-script is not about mp1 behavior, but: http://perl.apache.org/docs/2.0/user/config/config.html#C_SetHandler_
the problem is that SetHandler doesn't affect <Files > sections. If that's the case shouldn't Apache die when someone does that?
PerlResponseHandler ModPerl::Registry
# The following AddHandler is required in my current setup to make mod_perl
active.
AddHandler perl-script .pl
PerlOptions +ParseHeaders
Options +ExecCGI
# old
# SetHandler perl-script
# PerlHandler Apache::Registry
# Options ExecCGI
# PerlSendHeader ON
</Files>
</Directory>
</VirtualHost>
OK, so your problem was a simple misconfiguration. You simply weren't running under mod_perl and rightfully $ENV{MOD_PERL} wasn't set.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
