321191 - Download Manager: RANGE resume of downloads not working; also 'resume' silently fails after http keep-alive timeout

Status: RESOLVED DUPLICATE of bug 230870

(Toolkit :: Downloads API, defect)

Description

[Ken Johanson]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Under no circumstance was I able to get download resume (Http 1.1 Range requests) to work, using the download managers pause/resume and cancel/retry control, and not with any server. In fact no RANGE req headers are NEVER sent.

However all the test URLs that I tried work fine with wget, etc.

Also, the 'pause' function works fine as long as 'resume' is pressed with the keep-alive timeout period; however after the con is closed the download manager silently fails (should reconnect and try from zero?). And, http keep-alive durations are normally on the order of a few minutes (or even much less with heavy-use servers), so offering the user a pause control is tempting fate with large downloads.

Reproducible: Always

Steps to Reproduce:
1. Download a large file; abort then attempt 'cancel'/'retry' before keep-alive timeout; download progress bar starts again at zero.

2) Download a large file; click 'pause', then 'retry' after keep-alive timeout; download mgr says "complete".

Comment 1

[:Mook]

Duping to the general resume-after-connection-dies bug.  If I'm totally off-base on this, please reopen with an explaination on how this is separate, thanks.

-- random bug triaging monkey

*** This bug has been marked as a duplicate of 230870 ***

Comment 2

[Ken Johanson]

That bug is an RFE for resumable downloads between browser restarts, i.e. adding a persistent store of the last partial downloads (Url -> local file mapping etc).

*This* bug is for two problems: 'retry' (range request) not working, and 'pause' broken with keep-alive timeout. While bug 230870 makes two passing references to "it doesnt work for me", it neither mentions the difference in 'retry' vs 'resume' and non existant RANGE req headers, nor the separate keep-alive timeout problem.

Please treat this seriously, these two problems are EXTREMELY frustrating to anyone who expects them to work with large downloads in a poor connectivity environment.

Comment 3

[Ralf Hauser]

see a similar RFE in the apache world: http://issues.apache.org/bugzilla/show_bug.cgi?id=38214

shouldn't that also work for large uploads (posts of "multipart/form-data")?

Comment 4

[Mike Connor [:mconnor]]

This is a dupe of bug 230870

*** This bug has been marked as a duplicate of 230870 ***