httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49270] CGI Scripts block on large POST data when writing to stdout
Date Tue, 11 May 2010 12:40:12 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49270

--- Comment #2 from unknown <spam.isapi.redir.dll@web.de> 2010-05-11 08:40:10 EDT ---
Somehow you're right, somehow that behaviour can lead to trouble.
I did some further testing. Problem occurs when data to stdout > 64 KK AND post
data > 64 KB (or around that value) If one of them is below the 64 KB mark,
everything is fine. 

Think of a perl script that outputs large data (>64K). That script gets its
input via post with some arguments. Now somebody just posts data > 64 K. He
does this repeatedly. He does this very often. Eventually the server gets an
out of memory error, because there is not enough time to get a timeout. So
there are more and more perl interpreters running, doing nothing, consuming
memory. 

Why does the apache not output anything to stdout till it has read all the
post-data? Think of an upload cgi. You can't output the status, because the
status arrives when the whole file is uploaded, so the status is useless at
that time.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message