Rici Lake wrote:
On 2-Sep-04, at 10:51 PM, Ben Hopkins wrote:
Nope. There are two copies of libperl.so: one in the apache source
tree, and one in libexec.
That's normal. libperl.so is created in the source tree and then
copied into the right
place when you do make install.
However, you seem to
William McKee wrote:
On Thu, Sep 02, 2004 at 08:51:15PM -0700, Ben Hopkins wrote:
Nope. There are two copies of libperl.so: one in the apache source
tree, and one in libexec.
BUT that link said to use ldd to see what libperl.so is referenced in
the httpd executable. I did that and found N
> 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
On Thu, Sep 02, 2004 at 08:51:15PM -0700, Ben Hopkins wrote:
> Nope. There are two copies of libperl.so: one in the apache source
> tree, and one in libexec.
>
> BUT that link said to use ldd to see what libperl.so is referenced in
> the httpd executable. I did that and found NO reference to
Hi Brett,
This question appears to have nothing to do with modperl. I'd suggest
you try the beginners mailing list. You can sign up at
http://learn.perl.org.
William
--
Knowmad Services Inc.
http://www.knowmad.com
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.a
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
