List of HTTP status codes
response codes of the Hypertext Transfer Protocol
This article lists standard and notable non-standard HTTP response status codes. Standardized codes are defined by IETF as documented in Request for Comments (RFC) publications and maintained by the IANA. Other, non-standard values are used by various servers. The descriptive text after the numeric code – the reason phrase – is shown here with typical value, but in practice, can be different or omitted.
Standard codes
Status codes defined by IETF are listed below. Emphasized terms must, must not and should are interpretation guidelines as given by RFC 2119.
1xx informational response
An informational response indicates that the request was received and understood and is being processed. It alerts the client to wait for a final response. The message does not contain a body. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.
100 Continue
The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent, such as a POST request).
“List of HTTP status codes” enters the record as response codes of the Hypertext Transfer Protocol. Crown Archives preserves that source wording while asking what List, HTTP and status can confirm, complicate or overturn.
Why this record matters
“List of HTTP status codes” is worth following because a concise public description often conceals a longer documentary argument. Here, List, HTTP and status provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 6, 2026. The linked authority identifier is Q1123288. None of the 0 selected statements returned an explicit reference.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “List of HTTP status codes”, its source revision and the description used here.
- Expand the search: follow List of HTTP status codes primary sources, List of HTTP status codes archive and List research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “List of HTTP status codes”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “List of HTTP status codes” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.