-
Notifications
You must be signed in to change notification settings - Fork 1k
fix(baggage): do not percent-encode W3C baggage metadata #8682
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
Open
arimu1
wants to merge
4
commits into
open-telemetry:main
Choose a base branch
from
arimu1:fix/6771-baggage-metadata-no-percent-encode
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fb8a048
fix(baggage): do not percent-encode or decode W3C baggage metadata
arimu1 3a146dd
docs(baggage): clarify W3C property-value vs opaque metadata encoding
arimu1 20df8ae
fix(baggage): skip inject entries with invalid metadata charset
arimu1 32f5ae2
fix(baggage): use literal café in metadata charset test
arimu1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Backward-compat concern with pass-through: today's per-blob encoding makes inject defensive against arbitrary caller-supplied metadata. Removing it exposes new failure modes for existing callers:
,: downstream parser sees a phantom list-member.;/=in odd positions: property parses as a different shape at the peer.The spec allows producer discretion on non-conforming input ("the behavior is undefined... it MAY remove an offending
list-member...").Proposal: extend
baggageIsInvalidto validate metadata against the W3C property charset (tchar/baggage-octet/ OWS /=/;) and skip the entry on failure. This matches the existing precedent of dropping the entry when key or value is invalid, keeps output spec-conformant, and covers HTTP safety as a side effect (W3C set is a strict subset of HTTP field-value).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 20df8ae. Invalid metadata charset skips the entry.