|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #28625 Max POST size overflow
Submitted: 2004-06-03 20:18 UTC Modified: 2004-06-04 14:48 UTC
From: jordi at bunster dot org Assigned:
Status: Not a bug Package: HTTP related
PHP Version: 4.3.4 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: jordi at bunster dot org
New email:
PHP Version: OS:


 [2004-06-03 20:18 UTC] jordi at bunster dot org
Giving post_max_size a value equal or greater than 2GB on 
php.ini causes php to overflow the variable it uses to store 
that value. The result is log entries similar to this:

"POST Content-Length of 0 bytes exceeds the limit of 
-2147483648 bytes"

Reproduce code:
Set post_max_size to 2G or more on php.ini, execute a POST operation on a php script.

Expected result:
The POST operation should complete, according to the limits 
specified on php.ini

Actual result:
"POST Content-Length of 0 bytes exceeds the limit of 
-2147483648 bytes" or similar entries on the webserver 
logfile, POST fails.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2004-06-04 14:48 UTC]
PHP only supports signed integers, which only go to 2GB - 1. After that it 'overflows' to negative values. THis is not considered a bug but a feature.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Fri Feb 03 11:03:46 2023 UTC