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.

Processing

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

Early Hints

Used to return some response headers before final HTTP message.

OK

Standard response for successful HTTP requests.

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.

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.

Partial Content

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

Multi-Status

The message body that follows is by default an XML message.

Multiple Choices

Indicates multiple options for the resource from which the client may choose.

Moved Permanently

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

Found

The resource was found but at a different URI (temporarily).

See Other

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

Not Modified

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

Temporary Redirect

The request should be repeated with another URI, but future requests should still use the original.

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.

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 was valid, 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 per the Accept headers.

Proxy Authentication Required

The client must first authenticate itself with the proxy.

Request Timeout

The server timed out waiting for the request.

Conflict

The request could not be completed due to a conflict with the current state of the target resource.

Gone

The requested resource is no longer available and no forwarding address is known.

Length Required

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

Precondition Failed

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

Payload 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.

Unprocessable Entity

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 that 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.

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 its header fields are too large.

Unavailable For Legal Reasons

The server is denying access to the resource as a consequence of a legal demand.

Internal Server Error

A generic error message when an unexpected condition was encountered.

Not Implemented

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

Bad Gateway

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

Service Unavailable

The server is currently unavailable (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 protocol 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.

Network Authentication Required

The client needs to authenticate to gain network access.