Fix: Prevent broken traces when HttpClient content headers contain tracing headers. (#1843) #1888
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.
Thank you for submitting a pull request. Please review our contributing guidelines and code of conduct.
Description
Fixes #1843.
Prevents duplicate outgoing tracing headers, for HttpClient calls, by ensuring that the headers are only present as request headers, and that they do not also appear as content headers. An existing Integration Test was updated to ensure that the distributed trace is not broken when tracing headers are part of the Content Headers collection.
Author Checklist
Reviewer Checklist