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

client hints generally uses "headers" to refer to "header fields" #320

Closed
royfielding opened this issue Mar 31, 2017 · 1 comment
Closed

client hints generally uses "headers" to refer to "header fields" #320

royfielding opened this issue Mar 31, 2017 · 1 comment
Labels
client-hints editorial

Comments

@royfielding
Copy link
Member

The WG drafts that extend HTTP/1 should be consistent with the terminology of RFC7230 and RFC7231. That means s/headers/header fields/g;.
@mnot
Copy link
Member

mnot commented May 3, 2017

Seems to have been addressed.

@mnot mnot closed this as completed May 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
client-hints editorial
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mnot @reschke @royfielding