-
Notifications
You must be signed in to change notification settings - Fork 55
fix: handling of HTTP headers in EventStreams #1396
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #1396 +/- ##
=======================================
Coverage 94.35% 94.35%
=======================================
Files 339 339
Lines 19972 19983 +11
=======================================
+ Hits 18844 18855 +11
Misses 1128 1128
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
424147b
to
895866e
Compare
this change would need also update our product documentation, right? |
895866e
to
88dd6e7
Compare
88dd6e7
to
8934da7
Compare
To include all headers you have to explicitly set the additional_data_headers = * * If the header key is used for Authentication it will be redacted * To pick and choose which headers get included, list them as a comma delimited string in additional_data_headers e.g Host,Origin,X-Request-ID * Any header that starts with X-Envoy will be dropped
8934da7
to
19f774c
Compare
|
To include all headers you have to explicitly set the
additional_data_headers = *
If the header key is used for Authentication it will be redacted
To pick and choose which headers get included, list them as a comma delimited string in additional_data_headers e.g Host,Origin,X-Request-ID
Any header that starts with X-Envoy will be dropped
X-Trusted-Proxy,X-Forwarded-For,X-Real-IP will be dropped