Ken Simpson wrote:

Great. I'll look at the patch. There are no relevant diffs between
0.49 and 0.50 in the apr/network_io/unix/sockopt.c so the damage must
have occurred somewhere else.

Please double check that (may be the httpd-dev archives), I could be wrong.


That patch only affects the HTTP protocol handler
(http://www.apache.org/dist/httpd/patches/apply_to_2.0.49/CAN-2004-0493.patch)
so I don't think it could be responsible for this behaviour. Also, I
retested with 0.49 and the same problem is happening so.. who knows.

Oh, so may be it was always broken. Didn't you say that the problem was introduced in Apache 2.0.50?


Yup, I'll be on the move starting tomorrow, so I'm not sure when I'll be able to work on that. Ideally that should happen after 2.0 release, so we don't get new TODO things on the way and first glean out the existing ones. But feel free to work on those and we will help with any questions that you may have (but better post them to the dev list, as they are more technical than this list should care about).


Okay -- sorry I didn't know there was a dev list. I'll subscribe to
it.

http://perl.apache.org/maillist/dev.html

--
__________________________________________________________________
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

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to