stas2004/09/25 11:47:10
Modified:t/response/TestModperl merge.pm
Log:
style cleanup
Revision ChangesPath
1.9 +66 -65modperl-2.0/t/response/TestModperl/merge.pm
Index: merge.pm
===
RCS f
stas2004/09/25 11:48:18
Modified:t/response/TestModperl merge.pm
Log:
after moving to its own vhost fix the test to explicitly call
$r->subprocess_env to make PerlPassEnv APACHE_TEST_HOSTTYPE visible to
the process
Revision ChangesPath
1.10 +3 -0 modper
stas2004/09/25 11:51:58
Modified:t/response/TestModperl merge.pm
Log:
- revert the last attempt which didn't work
- add a temp workaround
Revision ChangesPath
1.11 +3 -4 modperl-2.0/t/response/TestModperl/merge.pm
Index: merge.pm
===
stas2004/09/25 12:01:15
Modified:t/response/TestDirective env.pm
Log:
add a temp workaround for the PerlPassEnv handling bug
Revision ChangesPath
1.5 +3 -0 modperl-2.0/t/response/TestDirective/env.pm
Index: env.pm
stas2004/09/25 12:30:07
Modified:t/response/TestModperl merge.pm
t/response/TestDirective env.pm
Log:
unbreak the workaround
Revision ChangesPath
1.12 +1 -1 modperl-2.0/t/response/TestModperl/merge.pm
Index: merge.pm
===
stas2004/09/25 16:27:10
Modified:src/modules/perl modperl_callback.c
.Changes
Log:
make sure that each handler callback starts with a pristine
tainted-ness state, so that previous callback calls won't affect the
consequent ones. Without this change any
stas2004/09/25 20:12:38
Modified:src/modules/perl modperl_callback.c
.Changes
Log:
if some code changes the current interpreter's tainted state to on,
the return value from the handler callback will be tainted, and we
fail to deal with that. So revert t
