Bug 137283 - Apache does not accept uploads larger than 512kb
Summary: Apache does not accept uploads larger than 512kb
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: httpd
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Joe Orton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-27 08:24 UTC by Florian Brand
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-27 09:17:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Florian Brand 2004-10-27 08:24:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914
Firefox/0.10.1

Description of problem:


When trying to upload a file larger than 512kb via PHP, I immediatly
get a "Document contains no data" error in any browser (tested w/
Mozilla, Opera, IE, Firefox). Tested also with another script.
PHP is configured to accept uploads up to 10MB.

Error Log Entry:
Requested content-length of 787247 is larger than the configured limit
of 524288

After some digging in the sources with Thomas Woerner, we believe the
culprit is protocol.c

We verified this problem also on FC3.

Version-Release number of selected component (if applicable):
httpd-2.0.46-40.ent

How reproducible:
Always

Steps to Reproduce:
1. have PHP script that does uploads (postnuke in our case)
2. configure PHP to accept larger uploads
3. upload file
4. Sadness. :)
    

Actual Results:  Requested content-length of 787247 is larger than the
configured limit of 524288

Expected Results:  no error?

Additional info:

Comment 1 Joe Orton 2004-10-27 09:17:40 UTC
"configured limit" -- "configured" being the important word!  In RHEL3
PHP parses request bodies in-memory, so a 512K limit is enforced by
default:

$ grep LimitRequest /etc/httpd/conf.d/php.conf
    LimitRequestBody 524288





Note You need to log in before you can comment on or make changes to this bug.