HTTP Status Codes

Continue

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

Switching Protocols

The requester has asked the server to switch protocols and the server confirms it will do so.

Processing

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

Early Hints

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

OK

The request has succeeded.

Created

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

Accepted

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

Non-Authoritative Information

The response is from a transforming proxy, so it may differ from the origin server's response.

No Content

The request succeeded but there is no content to return.

Reset Content

The server asks the client to reset the view that sent the request.

Partial Content

The server is sending only part of the resource (range requests).

Multi-Status

WebDAV: the message body carries multiple independent status codes.

Already Reported

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

IM Used

The server fulfilled the request and the response is a representation of the result of one or more instance manipulations.

Multiple Choices

The request has more than one possible response; the client must choose one.

Moved Permanently

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

Found

The resource is temporarily under a different URI.

See Other

The response is at a different URI and should be fetched with GET.

Not Modified

The resource has not been modified since the last request (conditional request).

Use Proxy

The requested resource must be accessed through the proxy given by the Location field. Deprecated.

Unused

Reserved: an earlier draft defined it for a protocol switch that was never shipped.

Temporary Redirect

The resource is temporarily at another URI, but future requests should use the original URI.

Permanent Redirect

The resource is permanently at another URI, and the method must not change.

Bad Request

The request could not be understood by the server due to malformed syntax.

Unauthorized

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

Payment Required

Reserved for future use.

Forbidden

The request was valid, but the server refuses to respond to it.

Not Found

The requested resource could not be found on the server.

Method Not Allowed

The request method is not supported for the requested resource.

Not Acceptable

The server cannot produce a response matching the Accept headers.

Proxy Authentication Required

Authentication is required through a proxy before the request continues.

Request Timeout

The server timed out waiting for the request. The client may repeat the request.

Conflict

The request could not be processed due to a conflict with the current state.

Gone

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

Length Required

A Content-Length header is required but was not sent.

Precondition Failed

One or more preconditions in the request headers evaluated to false.

Content Too Large

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

URI Too Long

The URI provided was too long for the server to process.

Unsupported Media Type

The media format of the requested data is not supported by the server.

Range Not Satisfiable

The Range header cannot be satisfied.

Expectation Failed

The expectation in the Expect header could not be met by the server.

I'm a teapot

The server refuses to brew coffee because it is a teapot (from the April Fools' RFC 2324).

Misdirected Request

The request was directed at a server that cannot produce a response for the target URI.

Unprocessable Content

The request was well-formed but contained semantic errors, such as failed validation.

Locked

WebDAV: the resource that is being accessed is locked.

Failed Dependency

WebDAV: the request failed because a previous request it depended on failed.

Too Early

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

Upgrade Required

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

Precondition Required

The origin server requires the request to be conditional.

Too Many Requests

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

Request Header Fields Too Large

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

Unavailable For Legal Reasons

The resource is unavailable for legal reasons.

Internal Server Error

The server encountered an unexpected condition.

Not Implemented

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

Bad Gateway

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

Service Unavailable

The server is currently unable to handle the request (overloaded or down).

Gateway Timeout

The server, acting as a gateway, did not get a response in time.

HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

Variant Also Negotiates

The server has an internal configuration error: the chosen variant is misconfigured.

Insufficient Storage

WebDAV: the server is unable to store the representation needed to complete the request.

Loop Detected

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

Not Extended

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

Network Authentication Required

The client needs to authenticate to gain network access.

Network Connect Timeoutunofficial

Some proxies return this when the network connection times out. Not an official code.