Proper support of Range requests #5367
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
7633101 to
4373759
Compare
4373759 to
6b08bbd
Compare
diocas
previously approved these changes
Oct 17, 2025
7b42832 to
dcf725a
Compare
e740e4d to
403de93
Compare
Up to now, Reva supported Range requests only when the requested content was copied into Reva's memory. This has now been improved: the ranges can be propagated upto the storage provider, which only returns the requested content, instead of first copying everything into memory and then only returning the requested ranges
403de93 to
1bd91d4
Compare
glpatcern
approved these changes
Oct 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Up to now, Reva supported Range requests only when the requested content was copied into Reva's memory. This has now been improved: the ranges can be propagated upto the storage provider, which only returns the requested content, instead of first copying everything into memory and then only returning the requested ranges