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.

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

UTF-8 encoding of value should be more clearly defined #100

Closed
aphillips opened this issue May 19, 2022 · 0 comments · Fixed by #101
Closed

UTF-8 encoding of value should be more clearly defined #100

aphillips opened this issue May 19, 2022 · 0 comments · Fixed by #101
Assignees
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@aphillips
Copy link

3.2.1.3 value
https://www.w3.org/TR/baggage/#value

A value contains UTF-8 encoded string. Any characters outside of the baggage-octet ranges of characters MUST be percent-encoded. Characters which are not required to be percent-encoded MAY be percent-encoded.

The value space appears to require that the UTF-8 character encoding form be used, but this is not explicitly stated. There is also no discussion of what happens with percent-encoded octets that do not match UTF-8. I would suggest the following edits:

A value contains a string whose character encoding MUST be UTF-8 [Encoding]. Any characters outside of the baggage-octet range of characters MUST be percent-encoded. Characters which are not required to be percent-encoded MAY be percent-encoded.

When decoding the value, percent-encoded octet sequences that do not match the UTF-8 encoding scheme MUST be replaced with the replacement character (U+FFFD).

@aphillips aphillips added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label May 19, 2022
@kalyanaj kalyanaj self-assigned this Jun 7, 2022
kalyanaj added a commit to kalyanaj/baggage that referenced this issue Jun 7, 2022
kalyanaj added a commit that referenced this issue Jun 8, 2022
Resolves #100 (UTF-8 encoding of value should be more clearly defined).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants