>
> Where is declared that $PerlRequire?
>
Inside a Perl section..., so PerlRequire inside the Perl Section triggers
perl_section_self_boot, which calls perl_section, which executes the
PerlRequire inside the Perl section
I think you see what I mean...
>
> Can you please try this in both pe
> Before this change, the walking of the %ApacheReadConfig:: namespace
> populated by a PerlRequire directive was ignored (or delayed).
>
> Because the
>
> SVt_PV: $PerlRequire = /opt/symphony/etc/httpd/startup.pl'
>
> from your trace I suspect that inside your script, you are PerlRequir'ing
> i
l Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 28, 2000 4:53 AM
Subject: cvs commit: modperl/src/modules/perl perl_config.c
> dougm 00/09/27 20:53:02
>
> Modified:src/modules/perl perl_config.c
> Log:
> fix %Ap
On Wed, 27 Sep 2000, Salvador Ortiz Garcia wrote:
> The 'push_array(cls->Perl...' in both cases can be put inside an else part
> for the 'if(PERL_RUNNING()) {' to make clear that the process were
> delayed.
good idea.
> btw, when i was making the patch, i realize that right now the inline
> P
On Wed, 27 Sep 2000, Doug MacEachern wrote:
> On Tue, 26 Sep 2000, Salvador Ortiz Garcia wrote:
>
> > IMHO the real problem relies in allow Perl{Module|Require} directives in
> > .htaccess files, The cls->PermModule and cls->PerlRequire arrays are both
> > in the per server part of mod_perl con
On Tue, 26 Sep 2000, Salvador Ortiz Garcia wrote:
> IMHO the real problem relies in allow Perl{Module|Require} directives in
> .htaccess files, The cls->PermModule and cls->PerlRequire arrays are both
> in the per server part of mod_perl config, so allow to modify them (in
> this case append to)
On 26 Sep 2000 [EMAIL PROTECTED] wrote:
> dougm 00/09/26 14:02:44
>
> Modified:.Changes
>src/modules/perl perl_config.c
> Log:
> fix for Perl{Module,Require} in .htaccess
>
> Revision ChangesPath
> 1.524 +3 -0 modperl/Changes
>
>
