HTTP Status Codes
Complete reference of HTTP response status codes organized by category. Search by code number or name.
1xx — Informational
Continue
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 (e.g., upgrading to WebSocket).
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 the 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 processing is not yet complete.
Non-Authoritative Information
The returned meta-information is from a local or third-party copy, not 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 asks 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 WebDAV response that conveys information about multiple resources.
Already Reported
Used in a WebDAV response to avoid enumerating the same collection members repeatedly.
IM Used
The server has fulfilled a GET request and the response is a representation of instance-manipulations applied.
3xx — Redirection
Multiple Choices
The request has more than one possible response. The client should choose one.
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Found
The URI of requested resource has been changed temporarily. The client should use the same method for future requests.
See Other
The server sent this response to direct the client to get the resource at another URI with a GET request.
Not Modified
The resource has not been modified since the last request. The client can use its cached version.
Temporary Redirect
The server sends this response to redirect the client to another URI with the same method.
Permanent Redirect
The resource is now permanently located at another URI. The client should use the same method.
4xx — Client Error
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
The client must authenticate itself to get the requested response.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Forbidden
The client does not have access rights to the content. Unlike 401, the server knows the client identity.
Not Found
The server cannot find the requested resource. The URL is not recognized.
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 defined in the request headers.
Proxy Authentication Required
Similar to 401 but authentication is needed to be done by a proxy.
Request Timeout
The server timed out waiting for the request from the client.
Conflict
The request conflicts with the current state of the server.
Gone
The requested content has been permanently deleted from the server with no forwarding address.
Length Required
The server rejected the request because the Content-Length header field is not defined.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
Request entity is larger than limits defined by the server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Range Not Satisfiable
The range specified by the Range header field in the request cannot be fulfilled.
Expectation Failed
The expectation given in the Expect request header could not be met by the server.
I'm a Teapot
The server refuses the attempt to brew coffee with a teapot. (April Fools RFC 2324)
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 server refuses to perform the request using the current protocol but may do so after the client upgrades.
Precondition Required
The origin server requires the request to be conditional to prevent lost updates.
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 requests a resource that is not available due to legal reasons (censorship).
5xx — Server Error
Internal Server Error
The server has encountered a situation it does not know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
The server, while acting as a gateway, got 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 is acting as a gateway and cannot get a response in time from the upstream server.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error in transparent content negotiation.
Insufficient Storage
The server is unable to store the representation needed to complete the request (WebDAV).
Loop Detected
The server detected an infinite loop while processing the request (WebDAV).
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 (e.g., captive portals).