Closed Bug 1060202 Opened 5 years ago Closed 5 years ago
HTTP Response timeout not working as configured in Firefox
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140716183446 Steps to reproduce: Try to generate a report that takes more than 7 minutes to generate Actual results: The report generated after seven minutes in Firefox V31 In firefox V30, It works as the configurations and get timeout message after 300 Sec and when the configuration get changed, it works as expectations Expected results: As configured in Firefox, the http response need to timeout after 300 Secs.
This was purposefully disabled in favour of keep-alive checking, as far as I can tell. See bug 1024015 for the discussion.
Severity: major → normal
Status: UNCONFIRMED → NEW
Component: Untriaged → Networking: HTTP
Ever confirmed: true
Priority: P2 → --
Product: Firefox → Core
Ok. I understand that, the timeout is supposed to work when we change the configuration network.http.tcp_keepalive.long_lived_connections to false. Then how and where to adjust the timeout seconds?
Hi Jithu, You can use the pref "network.http.response.timeout" to change the timeout if TCP keepalives are disabled.
As Gijs mentions in comment 1, this was disabled by default; that was in v31. So, I'm going to close out this bug, but if you can't get the timeout to work by disabling keepalives and configuring the pref, then please feel free to reopen it.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Hi, I changed network.http.tcp_keepalive.long_lived_connections to false and network.http.response.timeout to 60 and try to generate the report. Actual Result: Time out did not occur and report generated after 170 Secs. Expected Result: Timeout occur at 60 Secs
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Jithu, both short and long-lived tcp keepalives should be disabled. Please try disabling network.http.tcp_keepalive.short_lived_connections as well as .long_lived_connections.
OK. Its working. Thanks.
Status: REOPENED → RESOLVED
Closed: 5 years ago → 5 years ago
Resolution: --- → WORKSFORME
Thanks for confirming Jithu!
You need to log in before you can comment on or make changes to this bug.