💻Firefox 28+ Network Timeout Setting Breaks Big Downloads
Firefox's big download timeout is a pain
TL;DR
Firefox's 300-second network timeout setting hinders big downloads, making them unstable and non-resumable. Adjusting the setting to 0 or a large value in about:config fixes the issue, but it's been a problem since 2005.
Firefox 28 and newer have a 300-second network timeout setting that interferes with resuming large downloads and their stability. Setting network.http.response.timeout to 0 or a very large value in about:config makes downloads more stable and resumable. This issue has plagued users since at least 2005. Resumable downloads in Firefox rely on connection timeouts rather than .part files, and the browser ignores existing .part files without this option. Wget remains a stable alternative for resumable downloads.
Key Points
Firefox 28 and newer have a 300-second network.http.response.timeout setting.
Setting network.http.response.timeout to 0 or a large value in about:config fixes download stability.
Resumable downloads in Firefox rely on connection timeouts, not .part files.
The issue has been known since at least 2005, impacting many users.
Wget -c -O "$filename" "$url" is a stable workaround for resumable downloads.
Why It Matters
If you're downloading large files in Firefox, the 300-second timeout can make downloads unstable and non-resumable. Adjusting the network.http.response.timeout setting to 0 or a large value fixes the issue, but it's been a known problem since 2005. Wget remains a stable alternative for resumable downloads.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,569 builders reading daily.