HTTP status codes

The server has received the start of the request; the client should send the rest.

The server is switching protocols as the client asked.

The server is working on the request and has no response yet (WebDAV).

The server sends some headers ahead of the final response.

The request succeeded.

The request succeeded and a new resource was created.

The request was accepted, but processing is not finished yet.

The request succeeded, but a proxy changed the content on the way.

The request succeeded and the response has no content.

The client should reset the view that sent the request, for example a form.

The server delivers only the part of the resource the client asked for with a Range header.

The response carries several status codes for several operations (WebDAV).

The items were already listed earlier in this response and are not repeated (WebDAV).

The server returns the result of a delta encoding instead of the full resource.

The resource has several variants the client can choose from.

The resource has moved for good; future requests should use the new address.

The resource is temporarily at a different address.

The response can be fetched from another address with GET.

The resource has not changed since the last request; the cached copy is still valid.

The resource can only be reached through the given proxy. Deprecated.

No longer used; the code stays reserved.

Repeat the request with the same method at another address; the original address stays valid.

This and all future requests should go to the new address with the same method.

The server cannot process the request because of an error on the client side.

Authentication is required and is missing or has failed.

Reserved for future use; originally meant for payment systems.

The request was valid, but the server refuses access, for example for lack of permissions.

The requested resource was not found.

The request method is not allowed for this resource.

The server cannot deliver content that matches the Accept headers of the request.

The client must first authenticate with the proxy.

The server waited too long for the request.

The request conflicts with the current state of the resource, for example with simultaneous edits.

The resource has been removed for good and will not come back.

The request must state the length of its content.

A precondition given in the request is not met on the server.

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

The address is too long for the server.

The server does not support the media type of the content sent.

The requested part of the resource lies outside what is available.

The server cannot meet the requirement of the Expect header.

The server refuses to brew coffee with a teapot. An April Fools' joke from 1998.

The request went to a server that cannot produce a response for it.

The request is well-formed but contains semantic errors.

The resource is locked (WebDAV).

The request failed because an earlier request failed (WebDAV).

The server will not process the request because it might be replayed.

The client should switch to a different protocol, for example TLS.

The server requires the request to be conditional.

The client has sent too many requests in a short time.

A single header field or all header fields together are too large.

Access to the resource is blocked for legal reasons.

Generic error: something unexpected happened on the server.

The server does not know the method or cannot fulfil the request.

The server acts as a gateway or proxy and got an invalid response from the upstream server.

The server is currently unavailable, for example because of overload or maintenance.

The server acts as a gateway or proxy and got no response in time from the upstream server.

The server does not support the HTTP version of the request.

Content negotiation ends in a circular reference.

The server does not have enough storage to complete the request (WebDAV).

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

The request needs further extensions before the server can fulfil it.

The client must sign in to get network access, for example on a Wi-Fi portal.