Request X-Header no longer supported #1194
Comments
|
Decided to support headers in all future protocol versions (so far only in words). So we can support them in prm structures. |
cthulhu-rider
pushed a commit
to cthulhu-rider/neofs-node
that referenced
this issue
Mar 3, 2022
Signed-off-by: Leonard Lyubich <[email protected]>
Merged
aprasolova
pushed a commit
to aprasolova/neofs-node
that referenced
this issue
Mar 5, 2022
Signed-off-by: Leonard Lyubich <[email protected]>
cthulhu-rider
added a commit
that referenced
this issue
Feb 26, 2024
They are not supported since nspcc-dev/neofs-api#279. Now storage nodes process the current epoch only. Refs #1194. Signed-off-by: Leonard Lyubich <[email protected]>
cthulhu-rider
added a commit
that referenced
this issue
Feb 28, 2024
They are not supported since nspcc-dev/neofs-api#279. Now storage nodes process the current epoch only. Refs #1194. Signed-off-by: Leonard Lyubich <[email protected]>
cthulhu-rider
added a commit
that referenced
this issue
Feb 28, 2024
They are not supported since nspcc-dev/neofs-api#279. Now storage nodes process the current epoch only. Refs #1194. Signed-off-by: Leonard Lyubich <[email protected]>
cthulhu-rider
added a commit
that referenced
this issue
Feb 29, 2024
They are not supported since nspcc-dev/neofs-api#279. Now storage nodes process the current epoch only. Refs #1194. Signed-off-by: Leonard Lyubich <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After pre-release changes of NeoFS SDK
Clientcall parameters no longer support request X-Headers. Some components were tied to it. These headers are a detail of the particular version of the NeoFS API protocol, soClient, by design, should not support them in generic calls.We can configure
Clientwith version-dependent pre-call hook, which is going to be called only within a certain version. If communication version is different, hook isn't called.The text was updated successfully, but these errors were encountered: