-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: multi range request considers servers that do not return multi range #113
Conversation
cb7fa3d
to
26922e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
2023-07-27 conversation: this is connected to the backpressure work. This will get merged after @lidel takes a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hacdias once below is addressed, lgtm
…answer to multiple ranges
c029dbc
to
517e9e3
Compare
@laurentsenta can we get this released to unblock work on ipfs/boxo#369? We want to run the new tests in Boxo and Kubo. |
This PR updates the multi range request such that it counts for servers that are not able to reply with a multi range. When the client asks for a range request 3 things might happen:
multipart/byteranges
as Content-Type. Includes both ranges.Content-Type
of the actual data and theContent-Range
header with the first range. Body has first range body.Content-Type
of actual data, noContent-Range
. Body has full file.https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests