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

RFC 7230: inconsistency "response code" vs "status code" #94

Closed
reschke opened this issue Jun 19, 2018 · 1 comment
Closed

RFC 7230: inconsistency "response code" vs "status code" #94

reschke opened this issue Jun 19, 2018 · 1 comment
Assignees
@reschke
Labels
caching editorial erratum h1-messaging semantics

Comments

@reschke
Copy link
Contributor

reschke commented Jun 19, 2018

See https://www.rfc-editor.org/errata/eid4050
@reschke reschke self-assigned this Jun 19, 2018
@reschke reschke changed the title RFC 7230: inconsistency "response code vs status code" RFC 7230: inconsistency "response code" vs "status code" Jun 19, 2018
@reschke
Copy link
Contributor Author

reschke commented Jun 19, 2018

FWIW, the section defining them says "Response Status Codes".

Related: in -semantics, we currently say "status-code" several times. Probably due to the HTTP/1.1 ABNF element called that way. We should fix that as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reschke reschke

Labels
caching editorial erratum h1-messaging semantics
Milestone
No milestone
Development

No branches or pull requests
1 participant
@reschke