Posted on June 6th, 2014 No comments
If your web page dies in 5 minutes, it may not be a server-side issue
I recently ran into a situation where a long-running webpage would timeout after 5 minutes in Firefox. Every time, with no server logs generated.
I tried increasing the max_execution_time PHP configuration value with ini_set. That didn’t work. I tried set_time_limit() too, but to no avail.
After a whole lot of debugging PHP on the server side, I discovered the problem was not related to any timeout on the server configuration. The timeout problem results from a new invisible configuration value that was implemented in Firefox itself at version 29. If you’re running Firefox 28 or before, then there was no such default.
I tried it in Chrome and things worked fine.
If you use Firefox, please check your version. If you’re on version 29 then Firefox itself can be the culprit generating a timeout error. You might see, “Sorry, the page could not be displayed.” Try again in a few minutes, check your proxy settings, and so on.
To fix it:
- Quit and restart Firefox so only one tab is open.
- Go to about:config (type that into the address bar) and then click OK when you are warned that you are about to void your warranty.
- Navigate to the following config key: Network -> http -> request -> timeout
- and double click on 300
- Change it to a larger value, such as 3600 (1 hour), 7200 (2 hours), or 86400 (24 hours) – the value that works best for your application.
As you can see, the default timeout in Firefox 29 is 300 seconds, or 5 minutes.
See the accepted answer on support.mozilla.org/en-US/questions/998088 for the gory details.