I understand that, but that is not what I am asking.
Theoretically if CGI.pm requires PerlSetupEnv, then those scripts which
use CGI.pm should stop working..
they are working just fine..
the %ENV hash is being populated as well..
yet plain as day in httpd.conf it says PerlSetupEnv Off
what I'm asking is, why... ?
John K Sterling wrote:
>
> check the guide:
> http://thingy.kcilink.com/modperlguide/performance/PerlSetupEnv_Off.html
>
> > But %ENV population is expensive. Those who have moved to the Perl Apache API no
>longer need this extra %ENV
> > population, and can gain by turning it Off. Scripts using the CGI.pm module
>require PerlSetupEnv On because that
> > module relies on a properly populated CGI environment table.
> >
>
>_______________________________________________________________________________________
>
> JR Mayberry wrote:
>
> > Perhaps I am a bit confused about how this should be working...but..
> >
> > I have PerlSetupEnv set to Off in httpd.conf..
> >
> > yet in this sample script running as an Apache::Registry script:
> >
> > #!/opt/bin/perl
> >
> > use Data::Dumper;
> > my $r = Apache->request();
> > $r->send_http_header('text/plain');
> > print Dumper(\%ENV);
> >
> > its dumping out what appears to be a complete enviroment..
> >
> > what gives, shouldnt this be empty?
> >
> > there are some other Apache::Registry scripts which havent been
> > re-written to not use CGI.pm anymore, is it possible that 'use'ing
> > CGI.pm;' is forcing this to be turned back on?
> >
> > -confused
> >
> > --
--
______________________________________________________________________
JR Mayberry e-Vend.net Corporation
Programmer and Systems Administrator (888) 427-8743 x226 tel
[EMAIL PROTECTED] http://www.e-vend.net
************************************************************************
The information in this message (including attachments) is confidential.
If the reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original message.
***********************************************************************
