#22985 [Opn-Bgs]: max_input_time

2003-04-02 Thread sniper
 ID:   22985
 Updated by:   [EMAIL PROTECTED]
 Reported By:  excalibur at hub dot org
-Status:   Open
+Status:   Bogus
 Bug Type: *Configuration Issues
 Operating System: FreeBSD 4.8RC
 PHP Version:  4.3.1
 New Comment:

That just means your php.ini file is not read.
(or you mistyped the setting)

Still not bug.




Previous Comments:


[2003-04-01 08:29:39] excalibur at hub dot org

That was the bug I was pointing out :



[2003-04-01 08:28:58] excalibur at hub dot org

Understood, however that does not explain why if the max_input_time is
set to 600 in the php.ini file, it still is registered as a -1 on the
phpinfo() page and as such does not get used... Only by creating a
.htaccess file does that value seem to get registered and used...

 Ie, if I upload a file with out the .htaccess file defining the
parameter, I can not upload any file larger then 32 KBytes, but using
it allows me to upload a file that transfers within the 10 minute time
limit..



[2003-03-31 15:28:36] [EMAIL PROTECTED]

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

If max_input_time == -1, then the value of max_execution_time is used
in it's place.



[2003-03-31 11:25:33] excalibur at hub dot org

Hi All, 

 Ok, been doing some testing in relation to the file uploads issue to
help a client of mine and found the following issue. With 4.3.x the
max_input_time definition in the php.ini file seems to be ignored.
Regardless of what I set it to in that file, phpinfo() only shows a -1
in the field and subsequently I can not upload any files larger then
about 32 Kbytes. Anything more then that and the upload completes and
the file disappears. 

 Doing a quick search around the net shows that the -1 was supposed to
define unlimited time??

 When I use a .htaccess file and set the value via:

  php_flag max_input_time 600

 phpinfo() shows the proper information, and that the 600 has taken
affect. At this time I can upload files upto the limits set via:

 upload_max_filesize = XXM

 I have a feeling that one of two things is happening, the unlimited
time is not being taken into account (if that is what the -1 denotes),
or the value is not being used at all via the php.ini settings, but
forcing it via a .htaccess file causes the value to be set properly..





-- 
Edit this bug report at http://bugs.php.net/?id=22985edit=1



#22985 [Opn-Bgs]: max_input_time

2003-04-02 Thread sniper
 ID:   22985
 Updated by:   [EMAIL PROTECTED]
 Reported By:  excalibur at hub dot org
-Status:   Open
+Status:   Bogus
 Bug Type: *Configuration Issues
 Operating System: FreeBSD 4.8RC
 PHP Version:  4.3.1
 New Comment:

No, it won't be used if it's not in the right place.
(for one reason, there are others too.)




Previous Comments:


[2003-04-02 11:28:10] excalibur at hub dot org

It was my understanding that the php.ini file is used when it exists,
otherwise the default values are used, correct?



[2003-04-02 10:37:55] [EMAIL PROTECTED]

That just means your php.ini file is not read.
(or you mistyped the setting)

Still not bug.





[2003-04-01 08:29:39] excalibur at hub dot org

That was the bug I was pointing out :



[2003-04-01 08:28:58] excalibur at hub dot org

Understood, however that does not explain why if the max_input_time is
set to 600 in the php.ini file, it still is registered as a -1 on the
phpinfo() page and as such does not get used... Only by creating a
.htaccess file does that value seem to get registered and used...

 Ie, if I upload a file with out the .htaccess file defining the
parameter, I can not upload any file larger then 32 KBytes, but using
it allows me to upload a file that transfers within the 10 minute time
limit..



[2003-03-31 15:28:36] [EMAIL PROTECTED]

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

If max_input_time == -1, then the value of max_execution_time is used
in it's place.



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
http://bugs.php.net/22985

-- 
Edit this bug report at http://bugs.php.net/?id=22985edit=1



#22985 [Opn-Bgs]: max_input_time

2003-03-31 Thread iliaa
 ID:   22985
 Updated by:   [EMAIL PROTECTED]
 Reported By:  excalibur at hub dot org
-Status:   Open
+Status:   Bogus
 Bug Type: *Configuration Issues
 Operating System: FreeBSD 4.8RC
 PHP Version:  4.3.1
 New Comment:

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

If max_input_time == -1, then the value of max_execution_time is used
in it's place.


Previous Comments:


[2003-03-31 11:25:33] excalibur at hub dot org

Hi All, 

 Ok, been doing some testing in relation to the file uploads issue to
help a client of mine and found the following issue. With 4.3.x the
max_input_time definition in the php.ini file seems to be ignored.
Regardless of what I set it to in that file, phpinfo() only shows a -1
in the field and subsequently I can not upload any files larger then
about 32 Kbytes. Anything more then that and the upload completes and
the file disappears. 

 Doing a quick search around the net shows that the -1 was supposed to
define unlimited time??

 When I use a .htaccess file and set the value via:

  php_flag max_input_time 600

 phpinfo() shows the proper information, and that the 600 has taken
affect. At this time I can upload files upto the limits set via:

 upload_max_filesize = XXM

 I have a feeling that one of two things is happening, the unlimited
time is not being taken into account (if that is what the -1 denotes),
or the value is not being used at all via the php.ini settings, but
forcing it via a .htaccess file causes the value to be set properly..





-- 
Edit this bug report at http://bugs.php.net/?id=22985edit=1