Bug #16013 Updated: max execution time reached with slow connection

ID: 16013 Updated by: franck@sopac.org Reported By: franck@sopac.org -Status: Bogus +Status: Open Bug Type: *Web Server problem Operating System: linux+windows PHP Version: 4.1.2 New Comment: This is not a support question. I know how to increase the max support time. There is definitively a problem with php over slow link which make the product as bad as MS IIS for difficult environment. I'd like a developer to look into the matter and provide a sensible answer to this problem where php is dependent on the connection speed....It shouldn't be... Previous Comments: ------------------------------------------------------------------------ [2002-03-12 06:14:19] sniper@php.net The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php ------------------------------------------------------------------------ [2002-03-12 04:57:57] franck@sopac.org I'm not sure about the php version number as I experience the problem on other people servers from Fiji like www.hp.com When accessing a php page on a web server, if the link is of poor bandwidth then the max execution time can be reached stopping the download of the page. To test the problem, you have to be in poor network conditions, which is sometime difficult to achieve. Ideally the max execution time should be independent of the flow of data from the web server to the client. This bug seems similar to the max execution time of ASP in IIS where a client had 240seconds to download a page. The solution was to enable page buffering, where the page is first created internally then send to the client. On php, it does not seem to be exactly similar as 30 second, default setting, would stop most of the download of pages. This will put php at odd with accessibility issues for developing countries. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16013&edit=1