Skip to content
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.

Sign up for GitHub

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

Clarify no empty string allowed in baggage names #4144

Merged
merged 3 commits into from
Jul 15, 2024
Merged

Clarify no empty string allowed in baggage names #4144

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
04436b6
Clarify no empty string allowed in baggage names
XSAM Jul 11, 2024
05b9f20
Update specification/baggage/api.md
XSAM Jul 11, 2024
212602a
Merge branch 'main' into non-empty-baggage-name
XSAM Jul 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion specification/baggage/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ with _exactly one value_. This is more restrictive than the [W3C Baggage
Specification, § 3.2.1.1](https://www.w3.org/TR/baggage/#baggage-string)
which allows duplicate entries for a given name.

Baggage **names** are any valid UTF-8 strings. Language API SHOULD NOT
Baggage **names** are any valid, non-empty UTF-8 strings. Language API SHOULD NOT
restrict which strings are used as baggage **names**. However, the
specific `Propagator`s that are used to transmit baggage entries across
component boundaries may impose their own restrictions on baggage names.
Expand Down
Loading