|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #71744 max execution time doesn't take effect in php built-in server
Submitted: 2016-03-08 13:47 UTC Modified: 2016-03-11 10:19 UTC
From: memoword at 163 dot com Assigned:
Status: Not a bug Package: Built-in web server
PHP Version: 5.6.19 OS: Windows 7 sp1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
50 + 20 = ?
Subscribe to this entry?

 [2016-03-08 13:47 UTC] memoword at 163 dot com
The max_execution_time option in php.ini doesn't work in php built-in web server
The environment is windows 7 sp1 x64 ultimate with php-5.6.19-nts-Win32-VC11-x86
I use a new php.ini-development as my php.ini file and set max_execution_time to zero. Then make the scripts below as index.php.
Run the server: php -S localhost:8000 index.php
Then visit localhost:8000
After 60s it doesn't work anymore, and shows 'Fatal error: Maximum execution time of 60 seconds exceeded in D:\********\index.php on line 4'

Test script:
while(1) {
echo date('H:i:s').'<br />';

Expected result:
As I set max-execution-time to zero, the script should run forever.However it only works for 60s. When I set max-execution-time to 600, it still only works for 60s.
After 60s it doesn't work anymore, and shows 'Fatal error: Maximum execution time of 60 seconds exceeded in D:\********\index.php on line 4'

Actual result:
It stops after 60s.

When I run the server with php -S localhost:8000
and visit localhost:8000
It doesn't stop anymore even my max-execution-time is only 5


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2016-03-10 08:25 UTC]
-Status: Open +Status: Not a bug
 [2016-03-10 08:25 UTC]
Thanks for the report. I currently don't reproduce this behavior. From your description it is most likely a configuration issue. Default for max_execution_time is 30 seconds, but you tell it stops after 60 seconds. Most likely you load a wrong php.ini.

 [2016-03-11 10:19 UTC] memoword at 163 dot com
I realized that max_execution_time is 30 by default and I unexpectly found that when I change the max_input_time to -1, the time limitation disappeared. And it was set to 60 before I change it. That may means the execution time in built-in server is controlled by max_input_time...
 [2016-11-14 11:43 UTC] berarma at hotmail dot com
It does work but not like I would expect. And it doesn't seem well documented either.

Using PHP 5.6.27 in Debian Jessie. Although the built-in server uses the cli configuration it doesn't hardcode max_execution_time to 0.

max_execution_time: 30
max_input_time: 60

-> Fatal error: Maximum execution time of 60 seconds exceeded

max_execution_time: 30
max_input_time: -1

-> Fatal error: Maximum execution time of 30 seconds exceeded

max_execution_time: 0
max_input_time: -1

-> OK
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sun Aug 01 00:01:24 2021 UTC