Use Content-Range in multipart download for totalBytes #5101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change
TransferProgressUpdater
so it uses Content-Range header to determine the maximum number of bytes it tracks as part of the transfer progress listener.Motivation and Context
For downloads,
TransferProgressUpdater
was expecting the totalBytes of the whole s3 object to be the value of theContent-Length
header, when in fact theContent-Length
header only contains the size of the current part. This cause the value of transferred bytes to exceed to the number total byte expected as soon as a 2nd part was dowloaded.Modifications
Add a
ContentRangeParser
class to extract the total object size from theContent-Range
header, following the MDN refgerence. Only supportbytes
unit.Testing