RFC 7230, "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", June 2014

Source of RFC: httpbis (wit)

⚠ This RFC has been obsoleted!

Obsoleted by: RFC9110, RFC9112

Updated by: RFC8615

Errata-ID: 4050

Status:
Verified
Type:
Editorial
Reported By:
Daisuke Miyakawa
Date Reported:
2014-07-11
Verified by:
Barry Leiba
Date Verified:
2014-07-12

Section 3.2.4 says:

A server MUST reject any received request message that contains
whitespace between a header field-name and colon with a response code
of 400 (Bad Request).

It should say:

A server MUST reject any received request message that contains
whitespace between a header field-name and colon with a status code
of 400 (Bad Request).

Notes:

Basically HTTP RFCs seem to prefer "status code" over "response code". RFC 7231 Section 6 uses status code or "Response Status Code", but rarely uses the term "response code" (though it uses it, once). Some technical books actually refer those codes as "response codes". I tend to be confused with the mixture of those two terms.