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
A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request.
Early Hints
Used to return some response headers before final HTTP message.
OK
Standard response for successful HTTP requests.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.
No Content
The server successfully processed the request and is not returning any content.
Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
Partial Content
The server is delivering only part of the resource (byte serving) due to a range header sent by the client.
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
Tells the client to look at (browse to) another URL. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect.
See Other
The response to the request can be found under another URI using the GET method.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.
Temporary Redirect
In this case, the request should be repeated with another URI; however, future requests should still use the original URI.
Permanent Redirect
The request and all future requests should be repeated using another URI.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
Payment Required
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme.
Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.
Not Found
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
Method Not Allowed
A request method is not supported for the requested resource.
Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request.
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
Gone
Indicates that the resource requested is no longer available and will not be available again.
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 or resource does not support.
I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time.
Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Not Implemented
The server either does not recognize the request method, or it lacks the ability 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 (because it is 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.