Re: [mp2] Compatibility issue: Apache::ParseFormData vs. 1.99_15

2004-09-04 Thread Stas Bekman
Fred Moyer wrote: Fred, thanks for assistance, but your patch does not touch line 144 in ParseFormData.pm: Thanks for the spot. My point though was that if you're not comfortable with using the current libapreq release because it's developer release, then making the changes to Apache::ParseFormDa

Re: [mp2] Compatibility issue: Apache::ParseFormData vs. 1.99_15

2004-09-03 Thread Fred Moyer
> Fred, thanks for assistance, but your patch does not touch line 144 in > ParseFormData.pm: Thanks for the spot. My point though was that if you're not comfortable with using the current libapreq release because it's developer release, then making the changes to Apache::ParseFormData for compata

Re: [mp2] Compatibility issue: Apache::ParseFormData vs. 1.99_15

2004-09-03 Thread Stanislav Sinyagin
Fred, thanks for assistance, but your patch does not touch line 144 in ParseFormData.pm: return(Apache::FORBIDDEN); } here>>> my $rm = $r->remaining; if($args->{'post_max'} && ($rm > $args->{'post_max'})) { so, why should it fix the problem? It still accesses rema

Re: [mp2] Compatibility issue: Apache::ParseFormData vs. 1.99_15

2004-09-02 Thread Fred Moyer
> - removed: > > remaining - this method is not needed if the deprecated > $r->client_block methods aren't used, (use $r->read > $r->instead) > > This violates the compatibility with Apache::ParseFormData, which becomes > unusable. Currently this module is the on