Showing 62 of 62 status codes
1xx — Informational
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
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.
2xx — Success
OK
The request has succeeded. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The returned metadata is not exactly the same as available from the origin server.
No Content
The server successfully processed the request but 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 sent by the client.
Multi-Status
A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate.
Already Reported
Members of a DAV binding have already been enumerated in a previous reply and are not being included again.
IM Used
The server has fulfilled a GET request for the resource with instance-manipulations applied.
3xx — Redirection
Multiple Choices
There are multiple options for the resource that the client may follow.
Moved Permanently
This and all future requests should be directed to the given URI.
Found
The resource was found at a different URI temporarily.
See Other
The response can be found under another URI using a GET method.
Not Modified
The resource has not been modified since the last request.
Use Proxy
The requested resource is available only through a proxy.
Temporary Redirect
The request should be repeated with another URI but future requests should use the original URI.
Permanent Redirect
The request and all future requests should be repeated using another URI.
4xx — Client Error
Bad Request
The server could not understand the request due to invalid 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 schemes.
Forbidden
The client does not have access rights to the content.
Not Found
The server cannot find the requested resource. The most famous error code on the web.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Not Acceptable
The server cannot produce a response matching the list of acceptable values.
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 processed because of conflict in the current state of the resource.
Gone
The resource requested 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.
Precondition Failed
The server does not meet one of the preconditions specified in 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 does not support.
Range Not Satisfiable
The client has asked for a portion of the file the server cannot supply.
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324)
Misdirected Request
The request was directed at a server that is not able to produce a response.
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 which 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.
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 its header fields are too large.
Unavailable For Legal Reasons
The user requested a resource that is not available due to legal reasons (censorship).
5xx — Server Error
Internal Server Error
A generic error message when an unexpected condition was encountered.
Not Implemented
The server does not recognize the request method or lacks the ability to fulfil it.
Bad Gateway
The server was acting as a gateway and received an invalid response from the upstream server.
Service Unavailable
The server is not ready to handle the request. Common causes are maintenance or overloading.
Gateway Timeout
The server was acting as a gateway 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 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 (captive portals).