-
Notifications
You must be signed in to change notification settings - Fork 14
Support unsigned object GET/HEAD responses #719
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
Conversation
cthulhu-rider
commented
Jun 19, 2025
- based on and blocked by object: Deprecate verification fields in GET and HEAD responses neofs-api#334
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #719 +/- ##
==========================================
+ Coverage 59.17% 59.19% +0.01%
==========================================
Files 166 166
Lines 20950 20970 +20
==========================================
+ Hits 12397 12413 +16
- Misses 8287 8290 +3
- Partials 266 267 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
44ae535 to
09b6307
Compare
roman-khimov
left a comment
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.
How about checksums? Can we check them and have an option to disable these checks at the client level?
From nspcc-dev/neofs-api@7dd2d1d. Brought doc changes only. Signed-off-by: Leonard Lyubich <[email protected]>
They are deprecated since nspcc-dev/neofs-api#334. Signed-off-by: Leonard Lyubich <[email protected]>
ID of the object is essentially a checksum of its header. To prevent malicious data substitution or bugs, received headers should be verified against requested IDs. This makes `Client.ObjectHead` method to do it. Signed-off-by: Leonard Lyubich <[email protected]>
Some customers may want to self-check or not check. Signed-off-by: Leonard Lyubich <[email protected]>
09b6307 to
2d60282
Compare
Follow 9f8ec0c, f3437c5. Signed-off-by: Leonard Lyubich <[email protected]>
2d60282 to
666fbf8
Compare
Follow nspcc-dev/neofs-sdk-go#719 in request forwarding case. Refs #3396. Signed-off-by: Leonard Lyubich <[email protected]>
Continues b283606. Follow nspcc-dev/neofs-sdk-go#719 in request forwarding case. Refs #3396. Signed-off-by: Leonard Lyubich <[email protected]>
Continues ad60ee5. Follow nspcc-dev/neofs-sdk-go#719 in request forwarding case. Refs #3396. Signed-off-by: Leonard Lyubich <[email protected]>
Continues f0ce38e. Follow nspcc-dev/neofs-sdk-go#719 in request proxy case. Refs #3396. Signed-off-by: Leonard Lyubich <[email protected]>
Continues 041cdce. Follow nspcc-dev/neofs-sdk-go#719 in request proxy case. Refs #3396. Signed-off-by: Leonard Lyubich <[email protected]>