[API] Baggage - Trim white spaces and check for semi colon which isn't allowed octet#7009
Merged
Kielek merged 13 commits intoopen-telemetry:mainfrom Apr 20, 2026
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Towards #6816, #5210
Changes
BaggagePropagatorto trim optional whitespace (OWS) around=separatorswhen parsing the
baggageheader, as required by theW3C Baggage specification. This caused
incompatibility with .NET 10's default W3C propagator, which emits headers with
OWS (e.g.
key = value), resulting in spaces being URL-encoded as+inoutbound headers received by downstream services.
BaggagePropagatorto strip baggage properties (;metadata) from valueswhen parsing the
baggageheader. Semicolon is not a validbaggage-octetperthe W3C Baggage specification and must be interpreted as the start of a property,
not part of the value.
(#5210)
Merge requirement checklist
CHANGELOG.mdfiles updated for non-trivial changesI don't think this is non-trivial but let me know if I need to do this