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. to WebSocket.

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

Used to return some response headers before final HTTP message (Link preloading).

The request succeeded. The response body contains the requested resource.

The request succeeded and a new resource was created. Often returned after POST.

The request has been received but not yet acted upon. Used for async processing.

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

The request succeeded but there is no content to return. Common for DELETE requests.

The server fulfilled the request and wants the client to reset the document view.

The server is delivering only part of the resource due to a Range request header.

Provides status for multiple independent operations (WebDAV).

The members of a DAV binding have already been enumerated in a previous reply.

The server has fulfilled a GET request for the resource using instance manipulations.

The request has more than one possible response. The user-agent should choose one.

The URL of the resource has been changed permanently. Use the new URL.

The resource is temporarily at a different URL. The client should continue to use the original.

The response can be found at a different URL using a GET method.

The cached version is still valid. The client can use the cached response.

The resource is temporarily at another URL. Same method must be used for the redirect.

The resource is permanently at another URL. Same method must be used.

The server cannot process the request due to malformed syntax or invalid parameters.

The client must authenticate to get the requested response. Credentials are missing or invalid.

Reserved for future use. Some services use it for quota or payment issues.

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

The server cannot find the requested resource. The URL is not recognized.

The request method is not allowed for the target resource.

No content matches the criteria given in the Accept request header.

Authentication is needed to be done by a proxy.

The server timed out waiting for the request.

The request conflicts with the current state of the server, such as an edit conflict.

The resource has been permanently deleted and will not be available again.

The Content-Length header is required but was not defined.

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

The request body is larger than the server is willing or able to process.

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 cannot be fulfilled.

The expectation indicated by the Expect header cannot be met by the server.

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

The request was directed at a server that is not able to produce a response.

The request was well-formed but has semantic errors (e.g. validation failure).

The resource that is being accessed is locked (WebDAV).

The request failed due to a previous request failure (WebDAV).

The server is unwilling to risk processing a request that might be replayed.

The server refuses to perform the request using the current protocol.

The origin server requires the request to be conditional to prevent lost updates.

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

The server is unwilling to process the request because its header fields are too large.

The resource cannot legally be provided, e.g. censored by a government.

The server encountered an unexpected condition that prevented it from fulfilling the request.

The server does not support the functionality required to fulfill the request.

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

The server is not ready to handle the request. Common causes: down for maintenance or overloaded.

The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.

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

Transparent content negotiation for the request results in a circular reference.

The server cannot store the representation needed to complete the request (WebDAV).

The server detected an infinite loop while processing the request (WebDAV).

Further extensions to the request are required for the server to fulfill it.

The client needs to authenticate to gain network access (captive portals).