fix: Correct amount of bytes for HTTP range responses #64
+1
−1
Conversation
This file contains 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
The HTTP "Range" and "Content-Range" headers use inclusive start and end indices. See [RFC 7233](https://www.rfc-editor.org/rfc/rfc7233). Bun file slices, however, use an exclusive end index. The code to construct the answer did not reflect that.
|
Fixes #65 |
jeppech
added a commit
to jeppech/svelte-adapter-bun
that referenced
this pull request
Sep 30, 2024
|
@gornostay25, could you merge it? It's simple to review (literally 1 line). |
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.
The HTTP "Range" and "Content-Range" headers use inclusive start and end indices.
See RFC 7233.
Bun file slices, however, use an exclusive end index. The code to construct the answer did not reflect that.