TIMEOUTs are Browser dependent ...
Internet Explorer:
Internet Explorer imposes a time-out limit for the server to return data. By default, the time-out limit is as follows:
When the server is experiencing a problem, Internet Explorer does not wait endlessly for the server to return data.
Applications that use the WinINet API directly will experience the following ReceiveTimeout values:
You can locate the version of WinINet.dll in the %windir%\system32 directory.
How to change the IE ReceiveTimeout limit via Windows Registry:
Firefox:
Firefox user preferences can be viewed and modified by typing about:config in the Browser AddressBar.
ref:
Default timeout settings for Internet Explorer - http://support.microsoft.com/kb/181050, http://support.microsoft.com/kb/813827
Http Keep-Alive Timeouts of the Browsers - http://blog.fastmail.fm/2011/06/28/http-keep-alive-connection-timeouts/
HTTP Error 408 Request timeout
The Web server (running the Web site) thinks that there has been too long an interval of time between 1) the establishment of an IP connection (socket) between the client (e.g. your Web browser ) and the server and 2) the receipt of any data on that socket, so the server has dropped the connection. The socket connection has actually been lost - the Web server has 'timed out' on that particular socket connection. The request from the client must be repeated - in a timely manner.
408 errors in the HTTP cycle:
Any client (e.g. your Web browser) goes through the following cycle:
- Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
- Open an IP socket connection to that IP address.
- Write an HTTP data stream through that socket.
- Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
- This error occurs in the final step above when the client receives an HTTP status code that it recognizes as '408'. (Last updated: March 2012).
Internet Explorer:
Internet Explorer imposes a time-out limit for the server to return data. By default, the time-out limit is as follows:
| Internet Explorer 4.0 and Internet Explorer 4.01 | 5 minutes |
| Internet Explorer 5.x and Internet Explorer 6.x | 60 minutes |
| Internet Explorer 7 and Internet Explorer 8 | 60 minutes |
When the server is experiencing a problem, Internet Explorer does not wait endlessly for the server to return data.
Applications that use the WinINet API directly will experience the following ReceiveTimeout values:
| WinINet.dll version 4.x | 5 minutes |
| WinINet.dll versions 5.x and 6.x | 60 minutes |
| WinINet.dll versions 7.x and 8.x | 30 seconds |
You can locate the version of WinINet.dll in the %windir%\system32 directory.
How to change the IE ReceiveTimeout limit via Windows Registry:
- Start Registry Editor (Click Start, click Run, type regedit, and then click OK).
- Locate the following subkey:
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
- In this subkey, add a ReceiveTimeout DWORD entry that has the appropriate timeout value in milliseconds.
Firefox:
Firefox user preferences can be viewed and modified by typing about:config in the Browser AddressBar.
ref:
Default timeout settings for Internet Explorer - http://support.microsoft.com/kb/181050, http://support.microsoft.com/kb/813827
Http Keep-Alive Timeouts of the Browsers - http://blog.fastmail.fm/2011/06/28/http-keep-alive-connection-timeouts/