ID: 27703 Updated by: [EMAIL PROTECTED] Reported By: anarchy_rulz14 at hotmail dot com -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Windows XP PHP Version: 4.3.4 New Comment:
This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2004-03-25 16:12:26] anarchy_rulz14 at hotmail dot com Sorry, I put it there at first, then I accidentally moved it when I update the report. Sorry. ------------------------------------------------------------------------ [2004-03-25 16:10:29] [EMAIL PROTECTED] It's a deocumentation problem. ------------------------------------------------------------------------ [2004-03-25 15:28:46] anarchy_rulz14 at hotmail dot com PS. THis is the file manager i am using http://platon.sk/projects/phpWebFileManager/home.php ------------------------------------------------------------------------ [2004-03-25 15:25:24] anarchy_rulz14 at hotmail dot com Description: ------------ I am using PHP4.3.4 (as a module) on Apache 1.3.29 on a WinXP box. I put this as a documentation error, because I don't know where else to put an erroneous error message. I am currently running a file-management script on my server, and it always seemed to give me max_execution_time exceeded errors while uplaodign large files, regardless of what value I set in php.ini. After much trial and error, I have found that in fact it is NOT the max_execution time value that is being exceeded, but it is the max_input_time value that is being exceeded. For example (using a default version of php.ini): max_execution_time = 6000 max_input_time = 60 will produce the error, while: max_execution_time = 30 max_input_time = 6000 will produce no error. For the record, NO other values (besides max_execution_tiem and max_input_time) were modified in php.ini. So it would seem that the error message being output is erroneous, since it is infact the max_input_time which is being exceeded. The error message makes it difficult to track down the real culprit in this situation. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27703&edit=1
