Edit report at https://bugs.php.net/bug.php?id=44522&edit=1
ID: 44522 Updated by: s...@php.net Reported by: mail2lv at yahoo dot com Summary: http upload max_limits and file above 2GB Status: Open Type: Feature/Change Request -Package: Feature/Change Request +Package: *General Issues Operating System: All PHP Version: 5.2.5 Block user comment: N Private report: N New Comment: It's probably too late for 5.4, but would be OK for trunk. The patch however needs to be cleaned up (no IGNORE vars, etc.) and changing signature for zend_atoi may not be safe if any code out there presumes it returns int (integer overflow). Also, no reason to use signed long there where we used unsigned long. Previous Comments: ------------------------------------------------------------------------ [2012-02-23 10:14:23] jcabillot at gmail dot com Do you plan to apply this patch ? 5.3 doesn't support file upload if the file is bigger than 2Gb. It seem that 5.4 have the same limit. ------------------------------------------------------------------------ [2012-02-22 09:30:11] noxxim at mail dot ru Can someone add a patch for debian squeeze? ------------------------------------------------------------------------ [2010-02-15 19:52:50] zaulychny at yahoo dot com The same problem was faced by me. It seems that PHP stops if size of file is above 2Gb (i.e. signed int). Will someone fix this issue? ------------------------------------------------------------------------ [2009-12-09 20:40:19] tracey at archive dot org we are using 64-bit ubuntu (jaunty and karmic) at archive.org, and php v5.2.6 and v5.2.10 (respectively). we are using fastcgi php-cgi with nginx. for us, with these 2 patches, we can get up to 8G posting to work (haven't tried over 8GB 8-). basically, they are about tracking the config setting/reading vars that are 32bits wide when they'd need 64bits, and similar for upload limit checking and reading. they prolly will not work with 32bit ubuntu immediately without some minor tweaking (since i started using long (8B on 64bit; 4B on 32bit) datatype and stuck with it instead of "long long" (8B on both)). i'd be happy to try to extend the patches to work on both 32bit and 64bit if there is interest. (basically it took me awhile to figure these out and we are only running on 64bit so i'd want an incentive/encouragement to do the extra work 8-) http://www.archive.org/~tracey/downloads/patches/jaunty-64bit-post- large-files.patch http://www.archive.org/~tracey/downloads/patches/karmic-64bit-post- large-files.patch http://www.archive.org/~tracey/downloads/patches/jaunty-64bit-post- large-files.patch-README.txt ------------------------------------------------------------------------ [2009-04-24 09:12:04] robin at willowsv dot com It will accept 2047M Anything bigger breaks post data completely. You can only use GET variables. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=44522 -- Edit this bug report at https://bugs.php.net/bug.php?id=44522&edit=1
