HTTP Status Codes

Continue

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

Switching Protocols

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

Processing

A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request.

Early Hints

Used to return some response headers before final HTTP message. Allows the browser to start preloading resources.

OK

Standard response for successful HTTP requests. The actual response will depend on the request method used.

Created

The request has been fulfilled, resulting in the creation of a new resource.

Accepted

The request has been accepted for processing, but the processing has not been completed.

Non-Authoritative Information

The server is a transforming proxy that received a 200 OK from its origin but is returning a modified version of the origin's response.

No Content

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

Reset Content

The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.

Partial Content

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

Multi-Status

The message body that follows is by default an XML message and can contain a number of separate response codes.

Already Reported

The members of a DAV binding have already been enumerated in a preceding part of the multi-status response.

IM Used

The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

Moved Permanently

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

Found

Tells the client to look at (browse to) another URL. The request should be repeated with another URI, but future requests may still use the original URI.

See Other

The response to the request can be found under another URI using the GET method.

Not Modified

Indicates that the resource has not been modified since the version specified by the request headers.

Temporary Redirect

In this case, the request should be repeated with another URI, but future requests can still use the original URI.

Permanent Redirect

The request and all future requests should be repeated using another URI.

Bad Request

The server cannot or will not process the request due to an apparent client error such as malformed request syntax.

Unauthorized

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

Payment Required

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

Forbidden

The request contained valid data and was understood by the server, but the server is refusing action.

Not Found

The requested resource could not be found but may be available in the future.

Method Not Allowed

A request method is not supported for the requested resource.

Not Acceptable

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

Proxy Authentication Required

The client must first authenticate itself with the proxy.

Request Timeout

The server timed out waiting for the request.

Conflict

Indicates that the request could not be processed because of conflict in the current state of the resource.

Gone

Indicates that the resource requested was previously in use but is no longer available and will not be available again.

Length Required

The request did not specify the length of its content, which is required by the requested resource.

Precondition Failed

The server does not meet one of the preconditions that the requester put on the request header fields.

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 request entity has a media type which the server or resource does not support.

Range Not Satisfiable

The client has asked for a portion of the file, but the server cannot supply that portion.

Expectation Failed

The server cannot meet the requirements of the Expect request-header field.

I'm a Teapot

This code was defined in 1998 as one of the traditional IETF April Fools' jokes.

Misdirected Request

The request was directed at a server that is not able to produce a response.

Unprocessable Content

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

Locked

The resource that is being accessed is locked.

Failed Dependency

The request failed because it depended on another request and that request failed.

Too Early

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

Upgrade Required

The client should switch to a different protocol such as TLS/1.3.

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 ("rate limiting").

Request Header Fields Too Large

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

Unavailable For Legal Reasons

A server operator has received a legal demand to deny access to a resource or a set of resources.

Internal Server Error

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

Not Implemented

The server either does not recognize the request method, or it lacks the ability to fulfil the request.

Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

Service Unavailable

The server cannot handle the request (because it is overloaded or down for maintenance).

Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

HTTP Version Not Supported

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

Variant Also Negotiates

Transparent content negotiation for the request results in a circular reference.

Insufficient Storage

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

Loop Detected

The server detected an infinite loop while processing the request.

Not Extended

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

Network Authentication Required

The client needs to authenticate to gain network access.