+Entries added to C<%ENV> are passed on to the C<subprocess_env> table, +and are thus accessible via C<r-E<gt>subprocess_env> during the later +C<PerlLogHandler> and C<PerlCleanupHandler> phases.
and in sub-requests?
I dunno.
I also don't know if the above is true in all cases, such as when the handler scope is per-phase. but again, I wonder how many things we depend on (and document) change when the scope isn't for the entire request...
That has nothing to do with perl. Once it's in subprocess_env table it's there to stay till the end of the request. So filter, sub-requests, and latter phases can all see the env vars via C<r-E<gt>subprocess_env> .
> yeah, that too. sorry, I was only taking what you said at face value > because it made sense (and you nudged me to toward the docs :)
I hope at some point I won't need to nudge anybody and it'd be obvious that it's a goodness to document some conclusions after spending all this time figuring it out. ;)
> guess we still have more questions than answers at this point...
if you aren't sure about something, put it with a META tag, so we don't forget that it exists and polish it later. Or may be one of the nice users will do that for us.
__________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
