Perrin Harkins wrote:
On Thu, 2005-10-06 at 11:53 -0400, Jim Albert wrote:
Besides the fact that if I choose
the scripts to run mod_cgi perhaps in a non mod_perl environment,
then
they are all set to go.
This is true with Registry scripts as well.
I thought this was safer than calling C
On Thu, 2005-10-06 at 11:53 -0400, Jim Albert wrote:
> Besides the fact that if I choose
> the scripts to run mod_cgi perhaps in a non mod_perl environment,
> then
> they are all set to go.
This is true with Registry scripts as well.
> I thought this was safer than calling CGI::initiliaze_globa
Michael Peters wrote:
Jim Albert wrote:
Lack of response on this tells me:
1. Nobody is using ModPerl::PerlRun any longer to run their scripts
under mod_perl. I doubt it.
From the docs:
This module is meant for "Dirty" CGI Perl scripts
and
The Apache::Registry handler is much fast
Jim Albert wrote:
> Lack of response on this tells me:
>
> 1. Nobody is using ModPerl::PerlRun any longer to run their scripts
> under mod_perl. I doubt it.
>From the docs:
This module is meant for "Dirty" CGI Perl scripts
and
The Apache::Registry handler is much faster
So new developmen
Jim Albert wrote:
Lack of response on this tells me:
1. Nobody is using ModPerl::PerlRun any longer to run their scripts
under mod_perl. I doubt it.
Hopefully most people use Registry instead, but it has the same issue
with CGI.pm and subrequests.
2. There is an alternative to CGI.pm that
Lack of response on this tells me:
1. Nobody is using ModPerl::PerlRun any longer to run their scripts
under mod_perl. I doubt it.
2. There is an alternative to CGI.pm that is mod_perl safe. If there is
a mod_perl safe alternative to CGI.pm for use under ModPerl::PerlRun
scripts for things l
I think I may now have a better understanding of this and that the
problem lies in CGI.pm. I've emailed the following to Lincoln Stein
explaining what I believe to be true. Perhaps someone can either confirm
my understanding or otherwise correct me.
My email to Lincoln Stein is as follows:
I d
I'm trying to debug a strange situation with the following environment:
Apache 2.0.54
mod_perl 2.0.1
perl 5.8.6
CGI.pm 3.10
Linux 2.6.12-1.1447_FC4smp
Say I have a mod_perl script called x.cgi configured for mod_perl as
follows:
SetHandler perl-script
PerlHandler ModPerl::PerlRun
Options
