From 7a199a9e7fb31ca5cc9b2ab6e69170cff85eaf78 Mon Sep 17 00:00:00 2001 From: Sam Xie Date: Mon, 15 Jul 2024 13:00:08 -0700 Subject: [PATCH] Clarify no empty string allowed in baggage names (#4144) --- specification/baggage/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/baggage/api.md b/specification/baggage/api.md index 928ba2609c8..fef72cd153c 100644 --- a/specification/baggage/api.md +++ b/specification/baggage/api.md @@ -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.