Look for X-Headers within metaheader origin before APE check #1597
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1597
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-node:fix/1243_xheaders"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
origin
field ofMetaHeader
if the request has been forwarded from non-container node.When a request is forwarded to container node, metaheader is filled like that:
So, we expect x-headers may be found within
origin
(see also neo-node#1165)Close #1243
@ -479,0 +484,4 @@
// getXHeaders retrieves x-headers from a request. If the request is being forwarded, then
// x-headers may be found within `origin` field of meta header.
func getXHeaders(mh metaHeaderProvider) (res []session.XHeader) {
Why have you decided to introduce an interface and use
*Provider
argument instead ofgetXHeaders(*session.RequestMetaHeader) []session.XHeader
?The method is no longer actual as I used the approach suggested by @dstepanov-yadro
@ -479,0 +486,4 @@
// x-headers may be found within `origin` field of meta header.
func getXHeaders(mh metaHeaderProvider) (res []session.XHeader) {
res = mh.GetMetaHeader().GetXHeaders()
if len(res) == 0 {
See
meta := req.GetMetaHeader()
I think it should be the same.
The nesting can be more than 2 (theoretically).
It's very-very good point. Fixed!
Getting meta from origin (if it's present) should be enough for ape
50a4df4324
to4091fb64fa
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings