-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Envoy should not alter thrift THeader key #20595
Comments
Linking thrift issue requesting clarification on key format in the header spec |
Good catch, we should follow the spec. |
Fixes envoyproxy#20595. Signed-off-by: Yuxuan 'fishy' Wang <yuxuan.wang@reddit.com>
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
not stale |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.
Currently envoy always lowercase thrift THeader key and this is wrong
Description:
Thrift THeader keys are case-sensitive according to the spec, so altering them is a bug.
This is the line that does it:
envoy/source/extensions/filters/network/thrift_proxy/header_transport_impl.cc
Line 151 in 0fae697
Repro steps:
Make a thrift client and send "Foo: Bar" THeader to a thrift server via envoy. The server receives "foo: Bar" instead.
Admin and Stats Output:
Config:
Logs:
Call Stack:
The text was updated successfully, but these errors were encountered: