HTTP Status Code Reference
Complete reference of HTTP response status codes with explanations
1xx Informational
4Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
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
10OK
The request has succeeded. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and has resulted in a new resource being 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 and is asking the client to reset the 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.
Already Reported
Used inside a DAV: propstat response element to avoid enumerating members repeatedly.
IM Used
The server has fulfilled a GET request and the response represents the result of manipulations.
3xx Redirection
8Multiple Choices
There are multiple options for the resource that the client may follow.
Moved Permanently
The requested resource has been permanently moved to a new URL.
Found
The requested resource resides temporarily under a different URL.
See Other
The response to the request can be found under a different URL using GET method.
Not Modified
The resource has not been modified since the version specified in the request headers.
Use Proxy
The requested resource must be accessed through the proxy given by the Location field.
Temporary Redirect
The requested resource resides temporarily under a different URL.
Permanent Redirect
The requested resource has been definitively moved to the URL given by the Location headers.
4xx Client Error
29Bad Request
The server cannot process the request due to a client error (malformed syntax, invalid request).
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Forbidden
The server understood the request but refuses to authorize 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 requested resource can only generate content not acceptable according to 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 resource.
Gone
The requested resource 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 that the server cannot supply.
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
I'm a Teapot
Easter egg defined in RFC 2324. Any attempt to brew coffee with a teapot should result in this error.
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 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.
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 resource is unavailable due to legal demands (e.g., censorship).
5xx Server Error
11Internal Server Error
A generic error message when the server encounters an unexpected condition.
Not Implemented
The server does not recognize the request method or lacks the ability to fulfill it.
Bad Gateway
The server was acting as a gateway 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 and did not receive a timely response from upstream.
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.
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.