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

Expand on motivation for the encoding #213

Closed
martinthomson opened this issue Jul 18, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@martinthomson
Copy link
Contributor

commented Jul 18, 2016

Explain why you probably shouldn't just use UTF-8.

@reschke

This comment has been minimized.

Copy link
Contributor

commented Sep 2, 2016

...for new header fields?

@mnot mnot added the editorial label Sep 28, 2016

@mnot

This comment has been minimized.

Copy link
Member

commented Sep 28, 2016

Marking this as editorial, as I think it just means we need to point to 7230's restriction on header field values.

@reschke

This comment has been minimized.

Copy link
Contributor

commented Oct 5, 2016

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.

reschke added a commit that referenced this issue Oct 5, 2016

@reschke

This comment has been minimized.

Copy link
Contributor

commented Nov 14, 2016

I believe this can be closed with the changes in 5ec7eed

@reschke reschke closed this Nov 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.