I'm working on implementing PerlSetEnv/PerlPassEnv right now.
1. I see that SetEnv elem is missing from modperl_config_srv_t struct? I
can see it only in modperl_config_dir_t struct. Does that mean that we
cannot have a PerlSetEnv in httpd.conf's main level?
2. Regarding PerlPassEnv. It seems that currently *all* the enviroment
vars from shell are available at request time. At least that's what I see
when I run a test.
3. I still have problem with automatic configuration generation from
within test's __DATA__ section. Consider that I want this to be
autogenerated from the test response file:
PerlPassEnv HOME
<Location /TestDirective::perlpassenv>
SetHandler modperl
PerlResponseHandler TestDirective::perlpassenv
</Location>
So I put:
__DATA__
PerlPassEnv HOME
and I want it to be at the top level, not inside a container but I get it:
<Location /TestDirective::perlpassenv>
SetHandler modperl
PerlPassEnv HOME
PerlResponseHandler TestDirective::perlpassenv
</Location>
so currently I have to put it manually in Apache::PerlConfig, which sucks,
since it disconnects the test's conf bits from the test.
Is there a chance we can make things less magically DWIM and more
explicit DWIM?
e.g. let's specify top level as magic token __TOP__ and do:
__DATA__
<__TOP__>
PerlPassEnv HOME
</__TOP>
SomeDirective that goes inside autogenerated container
Or may be we should rethink the way __DATA__ is parsed and make it more
structured before we write too many tests based on the current rules, if
we think they change soon?
Thanks.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
