HTTP Status Codes

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 final HTTP message.

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

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

The request has been received but not yet acted upon.

The returned metadata is not exactly the same as available from the origin server.

There is no content to send for this request, but the headers may be useful.

Tells the user agent to reset the document which sent this request.

This response code is used when the Range header is sent from the client.

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

The request has more than one possible response.

The URL of the requested resource has been changed permanently.

The URI of requested resource has been changed temporarily.

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

Used for caching purposes. The response has not been modified.

The server sends this response to direct the client to get the requested resource at another URI with same method.

The resource is now permanently located at another URI, specified by the Location header.

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

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

Reserved for future use. Originally intended for digital payment systems.

The client does not have access rights to the content.

The server cannot find the requested resource.

The request method is known by the server but not supported by the target resource.

The server cannot produce a response matching the list of acceptable values.

Authentication is needed to be done by a proxy.

The server would like to shut down this unused connection.

The request conflicts with the current state of the server.

The requested content has been permanently deleted from server.

The server rejected the request because the Content-Length header is not defined.

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

Request entity is larger than limits defined by 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 in the request cannot be fulfilled.

The expectation given in the Expect request header cannot be met by the server.

The server refuses to brew coffee because it is, permanently, a teapot. (April Fools joke)

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

The resource that is being accessed is locked.

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

The user agent requested a resource that cannot legally be provided.

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, while working as a gateway, got an invalid response.

The server is not ready to handle the request. Common causes are maintenance or overload.

The server is acting as a gateway and cannot get a response in time.

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

The server is unable to store the representation needed to complete the request.

The server detected an infinite loop while processing the request.

The client needs to authenticate to gain network access.