You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by dorian <do...@scorched.broken.com> on 2000/06/22 03:47:01 UTC
Apache::Request and memory
Reply-To:
hm, i guess my post didn't seem to go through.
in regards to the handling of file uploads with Apache::Request -
i noticed that per file uploaded, the apache process grew approximately by the size of the file uploaded and stayed that way. could someone possibly point me into the direction that would help me deallocate this memory?
thanks
.djt
Re: Apache::Request and memory
Posted by Jim Winstead <ji...@trainedmonkey.com>.
Okay, I think I tracked this down to a one-byte buffer overflow.
Try the attached patch to see if that fixes it (it fixes things
in my testing).
Unfortunately, the overflow seemed to sneak through with no problems
on FreeBSD, and on Linux if you compile with -g.
Jim
On Jun 24, dorian wrote:
> breaks for me too. null byte issue maybe? i don't know. i can't write c. :)
>
> .djt
Re: Apache::Request and memory
Posted by dorian <do...@scorched.broken.com>.
breaks for me too. null byte issue maybe? i don't know. i can't write c. :)
.djt
Re: Apache::Request and memory
Posted by Matt Sergeant <ma...@sergeant.org>.
On Thu, 22 Jun 2000, Jim Winstead wrote:
> Attached is a patch to libapreq that addresses this problem.
Question for Doug,
Can we get libapreq 0.32 out any time soon? There are some pretty nasty
bugs in 0.31 that I'm waiting to get fixed. (the null cookies problem,
this problem, the form charset problem...)
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
Re: Apache::Request and memory
Posted by Jim Winstead <ji...@trainedmonkey.com>.
Attached is a patch to libapreq that addresses this problem.
(Doug, this may be updated since we last sent you this patch to
resolve issues with IE 4.5 on the Mac, which doesn't terminate the
MIME boundary correctly when there are <input type=image> fields
in a multipart/form-data form.)
Jim
On Jun 21, dorian wrote:
> Reply-To:
> hm, i guess my post didn't seem to go through.
> in regards to the handling of file uploads with Apache::Request -
> i noticed that per file uploaded, the apache process grew approximately by the size of the file uploaded and stayed that way. could someone possibly point me into the direction that would help me deallocate this memory?
>
> thanks
> .djt