HTTP Status Codes

The server has received the request headers and the client should proceed to send the request body.

The server is switching protocols as requested by the client (e.g., upgrading to WebSocket).

The server has received and is processing the request, but no response is available yet.

Used to return some response headers before the final HTTP message, allowing preloading of resources.

The request succeeded. The meaning depends on the HTTP method used.

The request succeeded and a new resource was created as a result.

The request has been accepted for processing, but processing is not yet complete.

The returned metadata is from a local or third-party copy, not the origin server.

The server successfully processed the request but is not returning any content.

The server successfully processed the request and asks the client to reset the document view.

The server is delivering only part of the resource due to a range header sent by the client.

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

Used inside a DAV response to avoid enumerating internal members of multiple bindings to the same collection.

The server has fulfilled a GET request and the response is a representation of one or more instance-manipulations.

The request has more than one possible response. The client should choose one of them.

The URL of the requested resource has been changed permanently. The new URL is given in the response.

The URI of requested resource has been changed temporarily. The client should continue to use the original URI.

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

The response has not been modified. The client can continue to use the cached version.

The server sends this response to redirect the client, preserving the HTTP method used.

The resource is now permanently located at another URI, preserving the HTTP method used.

The server cannot process the request due to something perceived to be a client error.

Authentication is required and has failed or has not been provided.

Reserved for future use. Some services use this for rate limiting or payment walls.

The client does not have access rights to the content. Unlike 401, the client's identity is known.

The server cannot find the requested resource. The most common error response on the web.

The request method is not supported for the requested resource.

The server cannot produce a response matching the list of acceptable values defined in the request headers.

Authentication with a proxy is required before the request can be served.

The server timed out waiting for the request from the client.

The request conflicts with the current state of the server.

The requested content has been permanently deleted from the server, with no forwarding address.

The server requires the Content-Length header field to be defined in the request.

The client has indicated preconditions in its headers which the server does not meet.

The request entity is larger than limits defined by the server.

The URI requested by the client is longer than the server is willing to interpret.

The media format of the requested data is not supported by the server.

The range specified by the Range header field in the request cannot be fulfilled.

The server refuses to brew coffee because it is a teapot (RFC 2324).

The request was well-formed but was unable to be followed due to semantic errors.

The user has sent too many requests in a given amount of time (rate limiting).

The resource is not available due to legal demands (e.g., censorship or government order).

The server has encountered a situation it does not know how to handle.

The request method is not supported by the server and cannot be handled.

The server, acting as a gateway or proxy, received an invalid response from the upstream server.

The server is not ready to handle the request, often due to maintenance or overload.

The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.

The HTTP version used in the request is not supported by the server.

The client needs to authenticate to gain network access (e.g., captive portal).