Continue
The client should continue the request or ignore if already finished.
Switching Protocols
The server understands and is willing to comply with the client's request for a change in the application protocol.
ProcessingDeprecated
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.
OK
The request succeeded. The result meaning depends on the HTTP method.
Created
The request succeeded, and a new resource was created as a result.
Accepted
The request has been received but not yet acted upon.
Non-Authoritative Information
The returned metadata is not exactly the same as is available from the origin server.
No Content
There is no content to send for this request, but the headers may be useful.
Reset Content
Tells the user agent to reset the document which sent this request.
Partial Content
This response code is used when the Range header is sent from the client.
Multi-Status
Conveys information about multiple resources in situations where multiple status codes might be appropriate.
Already Reported
Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings.
IM Used
The server has fulfilled a request for the resource, and the response is a representation of the result.
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 with a GET request.
Not Modified
This is used for caching purposes. It tells the client that the response has not been modified.
Temporary Redirect
The server sends this response to direct the client to get the requested resource with the same method.
Permanent Redirect
This means that the resource is now permanently located at another URI.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Unauthorized
The client must authenticate itself to get the requested response.
Payment Required
This response code is reserved for future use.
Forbidden
The client does not have access rights to the content.
Not Found
The server can not find the requested resource.
Method Not Allowed
The request method is known by the server but not supported by the target resource.
Not Acceptable
This response is sent when the web server cannot find any content conforming to the criteria given by the user agent.
Proxy Authentication Required
This is similar to 401 but authentication is needed to be done by a proxy.
Request Timeout
This response is sent on an idle connection by some servers.
Conflict
This response is sent when a request conflicts with the current state of the server.
Gone
This response is sent when the requested content has been permanently deleted from server.
Length Required
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 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
This response code means the expectation indicated by the Expect request header field cannot be met.
I'm a teapot
The server refuses the attempt to brew coffee with 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 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 and that request failed.
Too Early
Indicates that 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 unwilling to process the request because either header fields are too large.
Unavailable For Legal Reasons
The server is denying access to the resource as a consequence of a legal demand.
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
This error response means that the server got an invalid response while working as a gateway.
Service Unavailable
The server is not ready to handle the request.
Gateway Timeout
This error response is given when the server is acting as a gateway and cannot get a response in time.
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.
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
Indicates that the client needs to authenticate to gain network access.
About HTTP Status Codes
HTTP status codes are issued by a server in response to a client's request. They indicate whether the request was successful, redirected, resulted in an error, or requires further action. Each status code is a 3-digit number where the first digit defines the class of response.