Download service: Polish resume/retry logic on downloads which don't support range requests. |
|||
Issue descriptionProblem: In download service, call DownloadDriver::Resume will restart the download from beginning if, 1. the download doesn't support range request. AND 2. Server has timed out and close the connection. We should revisit our retry logic to see if we waste too much user data on non resumable downloads. Details are still need to be discussed. Something we can think of are: 1. Do we want to keep retrying on non resumable downloads? 2. Is there any scenario that we don't want to pause non resumable downloads since it's highly possible to restart from beginning, like user navigation or battery change events.
,
Aug 22 2017
We can get Accept-Range response header from download::DriverEntry::response_headers, or content::DownloadCreateInfo::accept_range.
,
Aug 23
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 23
PTAL |
|||
►
Sign in to add a comment |
|||
Comment 1 by xingliu@chromium.org
, Aug 22 2017