Orchestrator-workers on Twelve HTTP status codes, by the book

All twelve codes are covered by RFC 9110, "HTTP Semantics" (STD 97, June 2022), at https://www.rfc-editor.org/rfc/rfc9110.html. I did not open the page myself and relied on the three worker reports.

Which RFC is current: All three workers saw no "Obsoleted by" line on the RFC 9110 page and found no newer RFC in their searches. That is only a negative check. The rfc-editor info page returned 404, so I can't say it was positively confirmed.

Heuristic cacheability:

• Section 15.1 of RFC 9110 lists the heuristically cacheable codes as "200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, and 501", and says all other status codes are not heuristically cacheable.
• Worker group-c saw this text through a find result, and group-b saw it only as a search snippet. Neither read the full surrounding sentence.
• The workers also found explicit "is heuristically cacheable" statements in the sections for 203, 206, 308, 405, 410, 414 and 501.
• The sections for 303, 307, 413, 421 and 422 have no such statement, and those codes are not in the 15.1 list, so I marked them false.

Renamed reason phrases: 413 is now "Content Too Large", 414 is "URI Too Long" and 422 is "Unprocessable Content". Group-b reports 413 was "Payload Too Large" in RFC 7231. Group-c reports 414 was "Request-URI Too Long" in RFC 7231 and 422 was "Unprocessable Entity" in RFC 4918, but did not open either older RFC.

Quotes: Some quoted sentences wrap across lines in the page text (group-b noted this for 308, 405 and 413), so a checker may need to normalize whitespace.

{"answers":[
{"code":"203","reason":"Non-Authoritative Information","section":"15.3.4","heuristicallyCacheable":true,"quote":"This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might impact later decisions regarding the content.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"206","reason":"Partial Content","section":"15.3.7","heuristicallyCacheable":true,"quote":"A client MUST inspect a 206 response's Content-Type and Content-Range field(s) to determine what parts are enclosed and whether additional requests are needed.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"303","reason":"See Other","section":"15.4.4","heuristicallyCacheable":false,"quote":"This status code is applicable to any HTTP method.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"307","reason":"Temporary Redirect","section":"15.4.8","heuristicallyCacheable":false,"quote":"The user agent MAY use the Location field value for automatic redirection.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"308","reason":"Permanent Redirect","section":"15.4.9","heuristicallyCacheable":true,"quote":"The 308 (Permanent Redirect) status code indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"405","reason":"Method Not Allowed","section":"15.5.6","heuristicallyCacheable":true,"quote":"The origin server MUST generate an Allow header field in a 405 response containing a list of the target resource's currently supported methods.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"410","reason":"Gone","section":"15.5.11","heuristicallyCacheable":true,"quote":"A 410 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"413","reason":"Content Too Large","section":"15.5.14","heuristicallyCacheable":false,"quote":"If the condition is temporary, the server SHOULD generate a Retry-After header field to indicate that it is temporary and after what time the client MAY try again.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"414","reason":"URI Too Long","section":"15.5.15","heuristicallyCacheable":true,"quote":"The 414 (URI Too Long) status code indicates that the server is refusing to service the request because the target URI is longer than the server is willing to interpret.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"421","reason":"Misdirected Request","section":"15.5.20","heuristicallyCacheable":false,"quote":"A proxy MUST NOT generate a 421 response.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"422","reason":"Unprocessable Content","section":"15.5.21","heuristicallyCacheable":false,"quote":"For example, this status code can be sent if an XML request content contains well-formed (i.e., syntactically correct), but semantically erroneous XML instructions.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"code":"501","reason":"Not Implemented","section":"15.6.2","heuristicallyCacheable":true,"quote":"The 501 (Not Implemented) status code indicates that the server does not support the functionality required to fulfill the request.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"}
]}