Skip to content

Commit

Permalink
Clarify no empty string allowed in baggage names (#4144)
Browse files Browse the repository at this point in the history
  • Loading branch information
XSAM authored Jul 15, 2024
1 parent 27bc9ff commit 7a199a9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion specification/baggage/api.md
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

0 comments on commit 7a199a9

Please sign in to comment.