Bug #16880 Updated: max_execution_time affects large uploads

ID: 16880 Updated by: zebz@hotmail.com Reported By: zebz@hotmail.com -Status: Feedback +Status: Open Bug Type: Scripting Engine problem Operating System: Windows 98 PHP Version: 4.2.0 New Comment: Yes, Apache 1.3.xx Previous Comments: ------------------------------------------------------------------------ [2002-06-16 00:09:44] sniper@php.net Which webserver? Apache 1.3.xx? ------------------------------------------------------------------------ [2002-04-30 14:05:58] zebz@hotmail.com Will this bug be fixed on PHP 4.2.1? It makes huge uploads impossible without basically making the max_execution_time setting useless and I'm sure most hosts will refuse to set this setting to 10 minutes :( Someone reported having the same problem under Windows 2000 ------------------------------------------------------------------------ [2002-04-27 15:40:37] zebz@hotmail.com I recently upgraded PHP 4.1.2 to PHP 4.2 on my local Windows computer and it works a lot better for large uploads (no more huge RAM usage, etc). However I noticed that on this new version the max_execution_time setting counts the upload time, which doesn't make sense since the PHP script is called only after the file has been uploaded on the temp directory. set_time_limit() doesn't solve the problem since the time expires right before the script is called. For example if I set max_execution_time to 10 seconds and upload a 50Mb file, the file will take 20-30 seconds to be uploaded (remember, this is a local upload) and at the end I'll get a "Maximum execution time of 10 seconds exceeded" error. This would force anyone who wish to upload large files on a remote server to set the max_execution_time setting to 10 *minutes* or more, which, again, does not make sense. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16880&edit=1