Closed Bug 1063358 Opened 5 years ago Closed 4 years ago

Timeout screen appears after sometime.....


(Core :: Networking: HTTP, defect)

32 Branch
Not set





(Reporter: aalam, Unassigned, NeedInfo)



User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140830210550

Steps to reproduce:

I run an applicatoin job in firefox Version 32.

While following configurations appearing as '0' already, which was used in FF ver.30, and that case was fine in ver:30. But now it again appears with time set to '0'

type:     about:config

Search these and remove numeric values for:

Edit  > Preferences > Advanced >  Network > Settings > Mark check on 'Auto-Detect Proxy Settings for this Network'


Actual results:

But after sometime, response timeout appears.

Expected results:

Since all times alreaedy set to value=0, then no timeout error should appears.
Component: Untriaged → Networking: HTTP
Product: Firefox → Core
Do you mean network.http.response.timeout, and did you change that to 0 ? Does your server send keepalive packets? If not, disable both network.http.tcp_keepalive.short_lived_connections and network.http.tcp_keepalive.long_lived_connections to have the timeout setting take effect.
Blocks: 947391, 1024015
Flags: needinfo?(aalam)
(In reply to Asif Alam from comment #0)

Hi Asif - thanks for filing the bug! I have a couple of questions to add to Gijs' comment:

> network.http.keep-alive.timeout
> network.http.connection-timeout
> http.response.timeout

There are a lot of config changes listed in your description, so we need to sort through which one is causing the problem.

First off, can you list the config that you had in v30? And can you confirm that that config still works - we should confirm that there have been no changes in your network that are causing the timeout.

Second, can you try resetting all the values to default and see if the timeout occurs.

> Edit  > Preferences > Advanced >  Network > Settings > Mark check on
> 'Auto-Detect Proxy Settings for this Network'

Third, can you try disabling proxy usage in settings - 'No proxy'. We need to confirm that the proxy is working correctly.

Fourth, if default values and 'No proxy' fix the problem, can you change one piece of config at a time to help determine which one is causing the timeout.

Many thanks - help is greatly appreciated.
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.