-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Backport: router: fix a bug where header mutations may not be processed properly (#40856) #40904
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
envoyproxy#40856) Commit Message: router: fix a bug where header mutations may not be processed properly Additional Description: The envoyproxy#39534 introduced a bug where the `response_headers_to_add`` may be processed multiple times for local responses from the router filter. The sendLocalReply method will call the `finalizeResponseHeaders()` and the envoyproxy#39534 updated the code and make the `finalizeResponseHeaders()` be called in the modify_headers_ callback. This finally resulted in this problem. Risk Level: low. Testing: integration. Docs Changes: n/a. Release Notes: added. Platform Specific Features: n/a. Signed-off-by: WangBaiping <[email protected]>
|
/backport |
|
/retest |
1 similar comment
|
/retest |
|
seems like the release branches are also being hit with the go issue we fixed on main |
What should I do to fix it? 🤣 |
|
we will need to backport the fix first ... i can raise a pr for this branch now ... |
Thanks. |
Signed-off-by: code <[email protected]>
Signed-off-by: code <[email protected]>
phlax
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.
lgtm, thanks @wbpcode
Commit Message: router: fix a bug where header mutations may not be processed properly
Additional Description:
The #39534 introduced a bug where the `response_headers_to_add`` may be processed multiple times for local responses from the router filter.
The sendLocalReply method will call the
finalizeResponseHeaders()and the #39534 updated the code and make thefinalizeResponseHeaders()be called in the modify_headers_ callback. This finally resulted in this problem.Risk Level: low.
Testing: integration.
Docs Changes: n/a.
Release Notes: added.
Platform Specific Features: n/a.