HTTP Status Codes Reference
HTTP status codes are issued by a server in response to a client request. They indicate whether a request has been successfully completed, or if errors occurred. This comprehensive reference includes all standard status codes with explanations of when to use each one, RFC references, and practical examples.
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 is processing the request but no response is available yet.
Early Hints
Used to return some response headers before the final HTTP message.
OK
The request has succeeded.
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 has fulfilled the request but does not need to return a response body.
Reset Content
The server has fulfilled the request and the client should reset the document view.
Partial Content
The server is delivering only part of the resource due to a Range header.
Multi-Status
Multiple status codes for different operations.
Already Reported
The members of a DAV binding have already been enumerated.
Multiple Choices
The request has more than one possible response.
Moved Permanently
The URL of the requested resource has been changed permanently.
Found
The URI of requested resource has been changed temporarily.
See Other
The server sent this response to direct the client to get the requested resource at another URI.
Not Modified
Indicates that the resource has not been modified since the last request.
Use Proxy
The requested resource is available only through a proxy.
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with the same method.
Permanent Redirect
The resource is now permanently located at another URI.
Bad Request
The server cannot process the request due to malformed syntax.
Unauthorized
The client must authenticate itself to get the requested response.
Payment Required
Reserved for future use.
Forbidden
The client does not have access rights to the content.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The request method is known but not supported by the target resource.
Not Acceptable
The server cannot produce a response matching the Accept headers.
Proxy Authentication Required
Similar to 401 but authentication is required by a proxy.
Request Timeout
The server would like to shut down this unused connection.
Conflict
The request conflicts with the current state of the server.
Gone
The content has been permanently deleted from the server.
Length Required
The server refuses to accept the request without a defined Content-Length.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
The request entity is larger than limits defined by the server.
URI Too Long
The URI requested by the client is longer than the server can interpret.
Unsupported Media Type
The media format of the requested data is not supported.
Range Not Satisfiable
The range specified by the Range header cannot be fulfilled.
Expectation Failed
The expectation given in the Expect header cannot be met.
I'm a teapot
The server refuses to brew coffee because it is, permanently, a teapot.
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 could not be processed 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.
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.
Request Header Fields Too Large
The server is not willing to process the request because its header fields are too large.
Unavailable For Legal Reasons
The server cannot legally provide the resource.
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.
Bad Gateway
The server, while acting as a gateway, received an invalid response.
Service Unavailable
The server is not ready to handle the request.
Gateway Timeout
The server is acting as a gateway and cannot get a response.
HTTP Version Not Supported
The HTTP version used in the request is not supported.
Variant Also Negotiates
The server has an internal configuration error.
Insufficient Storage
The server cannot store the representation needed.
Loop Detected
The server detected an infinite loop in the request.
Not Extended
Further extensions to the request are required.
Network Authentication Required
The client needs to authenticate to gain network access.
Showing 61 of 61 HTTP status codes