TL;DR
An independent technical report describes changing Firefox’s network.http.response.timeout preference to zero or a much higher value as an experimental workaround for large downloads that fail to resume. The author says it only applies when the download server supports resuming and has not verified the suspected browser behavior in Firefox’s source code.
An independent report says changing Firefox’s network.http.response.timeout preference may help some large downloads resume after an interruption, addressing a problem the author says they encountered in testing. The proposed change is to set the preference to 0 or a much higher value, but the author has not confirmed why it appears to work, and it cannot make a download resumable if the server does not support that feature.
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The report, published on the personal site lunarwatcher.codeberg.page, says Firefox versions 28 and later use a default value of 300 seconds for the response-timeout preference. The author describes setting it to zero or a very large value through about:config as a way to make large downloads more resumable and “at least a little more stable.” These are observations from the author’s experiments, not results from a controlled test or a Mozilla statement.
The author suspects that Firefox’s handling of connection timeouts and retries may affect whether an interrupted download can continue. They also say Firefox may ignore an existing .part download file in some cases. The report does not establish that this is how Firefox’s download system works: its author says they have not checked the browser’s source code and do not know where to investigate.
The workaround has a firm limit: the server must support resumable downloads. The report says no browser preference can enable resuming when the server lacks that capability. For a separate option, the author mentions using wget -c to continue a download, describing that tool as more stable in their experience. That comparison is also based on personal use, not a published benchmark.
When a Timeout Can Interrupt a Download
For people downloading large files over unreliable connections, an interruption can mean waiting again or restarting from the beginning. If the report’s workaround works in a particular case, changing a timeout preference could help Firefox recover when a supported download fails. The practical value is conditional: the server must allow resumption, and the report does not show how often the setting helps or which specific failures it addresses.
The account is useful as a troubleshooting lead, not as a verified Firefox fix. It does not come from Mozilla, identify a tested Firefox release, or provide controlled comparisons across browsers and servers. Users should treat the suggested setting as an experiment rather than an official recommendation, particularly because the report does not document the effects of changing the timeout on other requests.
Products Worth Considering
Samsung 32 Odyssey G5 (G51F) QHD 180Hz Gaming Monitor
Samsung Odyssey OLED G5 27-Inch QHD Gaming Monitor
Anker SOLIX C1000 Gen 2 Portable Power Station with 200W Solar Panel
As an affiliate, we earn on qualifying purchases.
Firefox’s Timeout and Download History
The report says the preference has been set to 300 seconds since Firefox 28, a release dating to 2014, and describes that value as present in modern versions. It connects the setting to difficulty resuming some downloads, but offers no Mozilla documentation confirming that the default was designed to cause or prevent such behavior.
Resuming a download depends in part on support from the server delivering the file. The report distinguishes that server capability from a separate problem it believes may occur when Firefox fails to continue a download that could be resumed. It also mentions that download-resumption problems have existed in some form for many years, citing experience reaching back to 2005, but provides no specific bug record or release-by-release history.
“Setting network.http.response.timeout to 0 (or something very big) in about:config seems to make big downloads both resumable and at least a little more stable.”
— The report’s author
What the Timeout Change Has Not Proven
The report does not identify the Firefox version, operating system, servers, file sizes, or network conditions used in its experiments. It supplies no test data showing how often downloads resumed with the preference changed compared with the default. It is also unclear whether the timeout setting itself causes the observed difference, or whether other factors in the author’s tests contributed.
The account does not establish that Firefox relies on connection timeouts rather than partial files to resume downloads. The author presents that idea as a suspicion, and says they have not inspected the source code. No Mozilla response, official guidance, or confirmation that the preference remains applicable in current Firefox versions is included in the source material. The effect of setting the value to zero is not explained, either.
Further Testing Needed in Firefox
The next useful step would be repeatable testing across current Firefox versions, different servers known to support resuming, and controlled network interruptions. Tests would need to compare the default timeout with changed values and report whether a download continues, restarts, or fails. Checking Firefox source code or obtaining clarification from Mozilla could help establish whether timeouts and retry handling account for the reported behavior.
Until that evidence is available, the report leaves the setting as a possible user-tested workaround rather than an established fix. Anyone considering it should first confirm that the server supports resuming and should not assume the preference will solve every interrupted download. The source offers wget as an alternative, but does not provide comparative test results.
Key Questions
What Firefox setting does the report say to change?
It identifies network.http.response.timeout, which the author says is set to 300 seconds in Firefox 28 and later. The reported experiment changes it to zero or a much higher value using about:config.
Does changing the preference guarantee that a download will resume?
No. The report says the server must support resumable downloads, and presents the setting’s benefit as an observation from personal experiments, not a guaranteed result.
Has Mozilla confirmed this workaround?
The supplied report contains no Mozilla confirmation or official recommendation. Its author says they did not verify the proposed explanation against Firefox’s source code.
What alternative does the report mention?
The author says the command-line download tool wget -c worked for them as a way to continue a download. That is a personal account, not a controlled comparison with Firefox.
Source: hn
