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

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

reschke opened this issue Jun 19, 2018 · 1 comment


None yet
1 participant
Copy link

commented Jun 19, 2018

@reschke reschke self-assigned this Jun 19, 2018

@reschke reschke added the erratum label 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


This comment has been minimized.

Copy link
Contributor Author

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.

@reschke reschke closed this in f9f1a74 Jun 19, 2018

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.