-
Notifications
You must be signed in to change notification settings - Fork 126
fix(gateway): support suffix range requests #922
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
Changes from all commits
a1ae111
1147b6c
c30b27a
40f6d8d
ccc90f6
ee5383d
457423c
6274fc5
0328d78
7f26a32
0497ba8
4652c51
a7c67ae
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -219,10 +219,11 @@ type ContentPathMetadata struct { | |
// - From >= 0 and To = nil: Get the file (From, Length) | ||
// - From >= 0 and To >= 0: Get the range (From, To) | ||
// - From >= 0 and To <0: Get the range (From, Length - To) | ||
// - From < 0 and To = nil: Get the file (Length - From, Length) | ||
// | ||
// [HTTP Byte Range]: https://httpwg.org/specs/rfc9110.html#rfc.section.14.1.2 | ||
type ByteRange struct { | ||
From uint64 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💭 This triggered some AI checks – https://github.com/ipfs/boxo/security/code-scanning/7 – seems to be an issue already present in legacy code, unrelated to this PR. I don't think this is a problem blocking this PR because the gateway range-requests do not mutate UnixFS DAGs. Still, filled potential fix in #936 to make linter warning go away. |
||
From int64 | ||
To *int64 | ||
} | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.