HTTP Status Code Lookup

The initial part of a request has been received and the client should continue.

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

WebDAV: the server has received the request and is still processing it.

Used to return some response headers before the final HTTP message.

The request succeeded.

The request succeeded and a new resource was created.

The request was accepted for processing, but processing isn't complete.

The returned metadata isn't exactly from the origin server, but a copy or transformation.

The request succeeded but there is no content to send back.

The client should reset the document view that sent this request.

Only part of the resource was delivered, due to a range header.

WebDAV: conveys info about multiple resources in situations where multiple status codes apply.

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

The server fulfilled a GET request and the response is a representation of instance manipulations applied.

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

The resource has been permanently moved to a new URL.

The resource temporarily resides at a different URL.

The response can be found under a different URL using GET.

The resource hasn't changed since the last request (cache is valid).

Deprecated: the requested response must be accessed through a proxy.

No longer used; originally meant 'Switch Proxy'.

Like 302, but the request method must not change.

Like 301, but the request method must not change.

The server can't process the request due to a client error.

Authentication is required and has failed or not been provided.

Reserved for future use; occasionally used for APIs requiring payment.

The client doesn't have permission to access this resource.

The server can't find the requested resource.

The request method isn't supported for this resource.

No content matching the client's Accept headers was found.

Authentication with a proxy is required before the request can proceed.

The server timed out waiting for the request.

The request conflicts with the current state of the server.

The resource is no longer available and won't be available again.

The server requires a Content-Length header that wasn't provided.

A precondition in the request headers evaluated to false.

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

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

The media format of the request body isn't supported by the server.

The requested range can't be fulfilled given the size of the resource.

The expectation in an Expect header couldn't be met.

An April Fools' RFC joke status code; some servers use it playfully.

The request was directed at a server that can't produce a response.

The request was well-formed but contains semantic errors.

WebDAV: the resource being accessed is locked.

WebDAV: the request failed due to failure of a previous request.

The server is unwilling to process 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.

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

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

The resource is unavailable for legal reasons (e.g. censorship).

A generic error occurred on the server.

The server doesn't support the functionality required.

The server, acting as a gateway, got an invalid response upstream.

The server isn't ready to handle the request (overloaded or down).

The server, acting as a gateway, didn't get a response in time.

The HTTP version used in the request isn't supported by the server.

The server has an internal configuration error involving content negotiation.

WebDAV: the server can't store the representation needed to complete the request.

WebDAV: the server detected an infinite loop while processing the request.

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

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