Fix TChannel to gRPC tracing header leaksaving #2403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RELEASE NOTES:$tracing$ … protocol headers at TChannel ingress so they never enter application headers, sanitize gRPC metadata mapping to drop invalid and reserved keys, and derive inbound extraction from the request’s transport.
In order to prevents cross-transport leaks (and gRPC metadata errors) while keeping propagation intact across tchannle/http/grpc, in this PR, we strip