On Fri, Jun 04, 2004 at 03:05:36PM -0400, Perrin Harkins wrote:
> On Fri, 2004-06-04 at 14:49, Bill Moseley wrote:
> > With PerlSetupEnv OFF $cgi->param('foo') returns undef. I'm sure this
> > is suppose to work
>
> "Scripts using the CGI.pm module require PerlSetupEnv On because that
> module re
It so appears that in the last few years we get less and less mod_perl talks
and tutorials at the big (non-YAPC) conferences. And that's a bad trend. It
certainly affects the number of mod_perl job offers, since those who decide
which technology to choose for their next project go to those big c
[EMAIL PROTECTED] wrote:
I've run into another problem, but this one should be fairly straight
forward. I'm compiling mod_perl on a new server (Slackware 9.1,
Apache.2.0.48, and mod_perl 1.99_12 ), and am receiving the following
errors at the end of the test:
Sorry Zac, we are at mod_perl 1.99_14
On Fri, 2004-06-04 at 14:49, Bill Moseley wrote:
> With PerlSetupEnv OFF $cgi->param('foo') returns undef. I'm sure this
> is suppose to work
"Scripts using the CGI.pm module require PerlSetupEnv On because that
module relies on a properly populated CGI environment table."
http://perl.apache.org
I've run into another problem, but this one should be fairly straight
forward. I'm compiling mod_perl on a new server (Slackware 9.1,
Apache.2.0.48, and mod_perl 1.99_12 ), and am receiving the following
errors at the end of the test:
206ok
304ok
404...
With PerlSetupEnv OFF $cgi->param('foo') returns undef. I'm sure this
is suppose to work, so I'm wondering what I'm doing wrong.
CGI.pm 3.04, mod_perl 1.29
Here's a test config with a small handler:
ErrorLog error_log
PidFile httpd.pid
Listen *:5000
#PerSetupEnv Off
