-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add support for Range
header in object GET requests
#241
Conversation
Added function `formAllowRecord` to create `apiserver.Record`. Signed-off-by: Tatiana Nesterenko <tatiana@nspcc.io>
51776b3
to
cbda61a
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #241 +/- ##
==========================================
+ Coverage 22.12% 22.79% +0.66%
==========================================
Files 17 18 +1
Lines 3507 3672 +165
==========================================
+ Hits 776 837 +61
- Misses 2579 2677 +98
- Partials 152 158 +6 ☔ View full report in Codecov by Sentry. |
cbda61a
to
8813a62
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.
Please also add Accept-Ranges
8813a62
to
fae80c6
Compare
The `Range` header is now accepted for `/objects/{cid}/by_id/{oid}` and `/objects/{cid}/by_attribute/{oid}` requests. Close #224. Signed-off-by: Tatiana Nesterenko <tatiana@nspcc.io>
fae80c6
to
1d92ede
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.
Accept-Ranges?
Add the `Accept-Ranges` header into the API responses for `/objects/{cid}/by_id/{oid}` and `/objects/{cid}/by_attribute/{oid}`. `bytes` is the only accepted range unit. Signed-off-by: Tatiana Nesterenko <tatiana@nspcc.io>
Sorry, added. |
The
Range
header is now accepted for/objects/{cid}/by_id/{oid}
and/objects/{cid}/by_attribute/{oid}
requests.Close #224.