I should have mentioned that it was Apache 2.1.
anyway, I tested against apache 2.0 and 2.1 (cvs HEAD), worker and prefork, 5.8.0 and bleedperl (prefork only). everything is fine except for 2.1 worker.
I'll look closer at it tomorrow, but given that we don't support 2.1 officially yet...
ok, after last night's cvs HEAD builds, the last patch (stacked4.patch) seems to test fine (bugs that fix themselves. mmmm.)
tested variants include
/apache/2.0/prefork/bleedperl /apache/2.0/prefork/perl-5.8.0 /apache/2.0/prefork/perl-5.8.1-RC4 /apache/2.1/prefork/bleedperl /apache/2.1/prefork/perl-5.8.0 /apache/2.1/prefork/perl-5.8.1-RC4
/apache/2.0/worker/perl-5.8.0 /apache/2.1/worker/perl-5.8.0
so, give the patch a whirl. I'll commit next week if it works out for you.
what I tested with worked fine. As at the moment we don't support Apache 2.1 I think it's fine if it fails with it.
+1 to commit, but please write a doc for porting/compat.pod explaininig the change in the behavior and of course an entry in Changes.
__________________________________________________________________ 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]
