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

2004-09-02 Thread Stanislav Sinyagin
Hi all, In 1.99_15 changelog, - 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 t

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

2004-09-02 Thread Stanislav Sinyagin
Hi all, In 1.99_15 changelog, - 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 t

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