> Can't all these modules (your scripts,
The environment leak in my test case was just to make my point clear,
not a programmatic example of course
> mod_ssl, etc) just use the request object and/or Apache notes to
> communicate? That's exactly what they're there for!
I get it now: there is a kind of lost-update (actually, lost-delete)
problem because both mod_ssl and mod_perl try to write into the
environment, and cleanup in the wrong sequence (update 1-update
2-cleanup 1-cleanup 2). Thank you for helping me pointing it out.
> At least mod_perl can be told not to mess with the environment:
>
> <Directory /my/modperl/webroot>
> PerlSetupEnv Off
> </Directory>
Well sure, I even tried it but I use CGI.pm from Perl 5.6 and
CGI.pm> $meth=$ENV{'REQUEST_METHOD'} if defined($ENV{'REQUEST_METHOD'});
CGI.pm> [...]
CGI.pm> # If $meth is not of GET, POST or HEAD, assume we're being debugged
offline.
And there comes a funny message in my error log telling me
to enter name=value pairs on the standard input :-)
Your proposition, however righteous, means a lot of work for a lot
of people... Or perhaps Apache::Registry::handler should do some
tie()ing ? (yuck)
In the meantime, I will be cutting the StdEnvVars off from mod_ssl
configuration. Thanks again !
--
<< Tout n'y est pas parfait, mais on y honore certainement les jardiniers >>
Dominique Quatravaux <[EMAIL PROTECTED]>
