HTTP Status Code Reference

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

The requester has asked the server to switch protocols and the server has agreed.

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

Used to return some response headers before the final response.

Standard response for successful HTTP requests.

The request has been fulfilled and a new resource has been created.

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

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

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

This and all future requests should be directed to the given URI.

The resource was found but at a different URI. Tells the client to use the new URI for this request only.

The resource has not been modified since the last request. Use cached version.

Same as 302 but preserves the HTTP method.

Same as 301 but preserves the HTTP method.

The server cannot process the request due to a client error (malformed syntax).

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

The request was valid but the server is refusing to respond. The user may not have permissions.

The requested resource could not be found.

The request method is not supported for the requested resource.

The server timed out waiting for the request.

The request could not be processed because of conflict with the current state of the target resource.

The resource is no longer available and will not be available again.

The server cannot brew coffee because it is a teapot. (RFC 2324 joke status)

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

The user has sent too many requests in a given amount of time.

A generic error message for server failures.

The server does not recognize the request method or lacks the ability to fulfill it.

The server received an invalid response from an upstream server.

The server is currently unavailable (overloaded or down for maintenance).

The upstream server failed to respond in time.

The client needs to authenticate to gain network access.