Update baggage specification to clarify expectation when length is exceeded or when invalid entry is found - Githubissues

w3c / baggage

Propagation format for distributed context: Baggage

https://w3c.github.io/baggage/

Other

48 stars 18 forks source link

Update baggage specification to clarify expectation when length is exceeded or when invalid entry is found #80

Closed kalyanaj closed 2 years ago

kalyanaj commented 2 years ago

I was exactly looking for this to find what is language client implementation expected do in the case of certain cases

If number of baggage entries in the header exceed the maximum number of allowed entries, do we drop everything or do we drop extra entries and propagate the remaining entries?
If a baggage entry is invalid as per the definition, do we drop entire baggage or just that one entry?

This is not clear from spec. I would really appreciate some clarification here.

Thanks

Originally posted by @lonewolf3739 in https://github.com/w3c/baggage/issues/74#issuecomment-937995112