Our HTTP reference library maps each status code to standards-based semantics and real remediation paths for API and web teams. Every page clarifies when a response is expected, when it signals a defect, and how to verify the fix in production traffic.
Showing 1-15 of 62.
HTTP 100 Continue is an informational success code indicating that the server has received the request headers and the client is cleared to transmit the request body. It serves as a bandwidth-saving handshake for large-scale data uploads.
HTTP 101 Switching Protocols is an informational success response indicating that the server agrees to switch the application protocol of the current connection. It is the mandatory handshake response for establishing WebSockets (wss://) or upgrading to HTTP/2.
HTTP 102 Processing is a deprecated informational status code primarily used in WebDAV environments. It acts as an interim response to tell the client that a long-running request (like COPY or MOVE) is still active, preventing a connection timeout before a final response is sent.
HTTP 103 Early Hints is an informational response sent by the server before the final status code. It contains Link headers that allow browsers to begin preloading critical resources-like CSS, JavaScript, and Fonts-while the server is still processing the main request.
HTTP 200 OK means the request succeeded and the server is returning a representation of the target resource in the response body.
HTTP 201 Created means the request succeeded and a new resource was created as a result. The server should return the new resource URI in the Location response header.
HTTP 202 Accepted is a success status code indicating that a request has been received but processing is not yet complete. It is the gold standard for asynchronous operations, allowing the server to decouple request acknowledgment from task execution.
HTTP 203 Non-Authoritative Information is a success status code indicating that the request was successful, but the enclosed payload has been modified by a transforming proxy or API gateway from the origin server's original 200 OK response.
HTTP 204 No Content is a success status code indicating that the server has fulfilled the request but there is no data to return in the response body. It is the standard response for successful DELETE operations and PUT updates where no representation is needed.
HTTP 205 Reset Content is a success status code that instructs the client to reset the document view that initiated the request. It is the semantic standard for clearing form inputs or resetting a UI state after a successful submission without providing a response body.
HTTP 206 Partial Content is a success response indicating that the server is sending only a specific portion of a resource, as requested by the client via a Range header. It is the architectural backbone of video streaming, resumable large-file downloads, and multi-part byte-serving.
HTTP 207 Multi-Status is a success response indicating that the server has processed a batch request and the body contains multiple independent status codes for each sub-operation. It allows for "Partial Success," where some items in a batch succeed while others fail.
HTTP 208 Already Reported is a success status code used exclusively within a 207 Multi-Status response. It indicates that a resource has already been listed in a previous part of the same response, preventing redundant data and infinite loops in hierarchical collections.
HTTP 226 IM Used is a success status code indicating that the server has fulfilled a GET request by returning a "delta" (a set of changes) rather than the full resource. It requires the client to apply these instance manipulations to a previously cached base version.
HTTP 300 Multiple Choices means the target has more than one representation and the client should choose one.