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.

Sign up for GitHub

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

Jump to bottom

US-ASCII #696

Closed
martinthomson opened this issue Jan 28, 2021 · 0 comments
Closed

US-ASCII #696

martinthomson opened this issue Jan 28, 2021 · 0 comments
Assignees
@reschke
Labels
editorial has-proposal semantics

Comments

@martinthomson
Copy link
Contributor

In Section 5.5:

Newly defined fields SHOULD limit their values to US-ASCII octets.

This is probably overly broad considering that the ABNF says VCHAR / SP / HTAB (I question the wisdom of including HTAB, but now is not the time to worry about that). Could this be changed to "printable or visible US-ASCII octets, plus SP and HTAB"?

(Incidentally, why doesn't the field-content rule use the ABNF WSP rule?)
@reschke reschke self-assigned this Jan 31, 2021
royfielding added a commit that referenced this issue Jan 31, 2021
@royfielding
Merge pull request #718 from httpwg/reschke-696
31f46f4 
Values of newly defined fields should only use VCHAR/SP/HTAB (fixes #696)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reschke reschke

Labels
editorial has-proposal semantics
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @reschke