HTTP Status Codes Reference
Complete reference for HTTP response status codes from 1xx to 5xx
About HTTP Status Codes
Most Common Status Codes
The HTTP status codes you'll encounter most frequently
OK
The request has succeeded
Created
The request has been fulfilled and resulted in a new resource being created
No Content
The server successfully processed the request and is not returning any content
Moved Permanently
This and all future requests should be directed to the given URI
Found
The resource resides temporarily under a different URI
Bad Request
The server cannot process the request due to client error
Unauthorized
Authentication is required and has failed or has not been provided
Forbidden
The server understood the request but refuses to authorize it
Not Found
The requested resource could not be found
Internal Server Error
A generic error message when the server encounters an unexpected condition
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)
Informational (100–103)
These codes indicate that the request was received and understood.
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
Success (200–206)
These codes indicate the action requested was received, understood, and accepted.
OK
The request has succeeded
Created
The request has been fulfilled and 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 server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version
No Content
The server successfully processed the request and is not returning any content
Reset Content
The server successfully processed the request and the user agent should reset the document view
Partial Content
The server is delivering only part of the resource due to a range header sent by the client
Redirection (300–308)
These codes indicate the client must take additional action to complete the request.
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 resides temporarily under a different URI
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 by request headers
Temporary Redirect
The request should be repeated with another URI but future requests should still use the original URI
Permanent Redirect
The request and all future requests should be repeated using another URI
Client Error (400–451)
These codes indicate the request contains bad syntax or cannot be fulfilled.
Bad Request
The server cannot process the request due to client error
Unauthorized
Authentication is required and has failed or has not been provided
Payment Required
Reserved for future use in digital payment systems
Forbidden
The server understood the request but refuses to authorize it
Not Found
The requested resource could not be found
Method Not Allowed
The request method is not supported for the requested resource
Not Acceptable
The requested resource is capable of generating only 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 processed because of conflict in the current state of the resource
Gone
The resource is no longer available and will not be available again
Length Required
The request did not specify the length of its content
Precondition Failed
The server does not meet one of the preconditions in the request headers
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, but the server cannot supply that portion
Expectation Failed
The server cannot meet the requirements of the Expect request-header field
I'm a teapot
April Fools' joke from 1998; 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 contains 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
Request Header Fields Too Large
The server is unwilling to process the request because header fields are too large
Unavailable For Legal Reasons
The resource is unavailable due to legal reasons
Server Error (500–511)
These codes indicate the server failed to fulfill a valid request.
Internal Server Error
A generic error message when the server encounters an unexpected condition
Not Implemented
The server does not support the functionality required to fulfill the request
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
The server has an internal configuration error
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