We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Explain why you probably shouldn't just use UTF-8.
The text was updated successfully, but these errors were encountered:
...for new header fields?
Sorry, something went wrong.
Marking this as editorial, as I think it just means we need to point to 7230's restriction on header field values.
We already say:
"By default, header field values in HTTP messages ([RFC7230]) cannot directly carry characters outside the US-ASCII coded character set ([RFC0020])."
...which hints at the fact that RFC 7230 puts non-ASCII octets into the "obs-text" production. I'll try to expand a bit on this.
rewrite parts of the introduction, giving more motivation (#213)
5ec7eed
I believe this can be closed with the changes in 5ec7eed
No branches or pull requests
Explain why you probably shouldn't just use UTF-8.
The text was updated successfully, but these errors were encountered: