Practical use case for tokens attached to the request wrappers #878

Open
opened 2025-12-28 17:21:00 +00:00 by sami · 0 comments
Owner

Originally created by @carpawell on GitHub (Nov 11, 2022).

I faced some bug (or not) in #2045 while was testing request forwarding: a node took tokens from the first MetaHeader it has and did not try to unwrap any other despite the fact that for example, the ACL service checks the deepest one only. Was it a bug? Do we have any info about how to treat sessions/bearers attached to the wrappers not the original requests?

/cc @cthulhu-rider, @realloc, @alexvanin, @fyrchik

Originally created by @carpawell on GitHub (Nov 11, 2022). I faced some bug (or not) in #2045 while was testing request forwarding: a node took tokens from the first `MetaHeader` it has and did not try to unwrap any other despite the fact that for example, the ACL service checks the deepest one only. Was it a bug? Do we have any info about how to treat sessions/bearers attached to the wrappers not the original requests? /cc @cthulhu-rider, @realloc, @alexvanin, @fyrchik
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#878
No description provided.