| Value | HTTP 1.1 | Description |
|---|---|---|
| 1xx | Informational | |
| 100 | HTTP_CONTINUE | The client may continue with its request. |
| 101 | HTTP_SWITCHING_PROTOCOLS | The server understands and is willing to comply with the client's request, via the Upgrade message header field, for a change in the application protocol being used on this connection. |
| 102 | HTTP_PROCESSING | (WebDAV; RFC 2518) As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost. |
| 2xx | Success | |
| 200 | HTTP_OK | The request has succeeded. |
| 201 | HTTP_CREATED | The request has been fulfilled and resulted in a new resource being created. |
| 202 | HTTP_ACCEPTED | Indicates the request has been accepted for processing, but the processing has not been completed. |
| 203 | HTTP_NON_AUTHORITATIVE | The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. |
| 204 | HTTP_NO_CONTENT | The server has fulfilled the request but there is no new information to send back. |
| 205 | HTTP_RESET_CONTENT | The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. |
| 206 | HTTP_PARTIAL_CONTENT | The server has fulfilled the partial GET request for the resource. |
| 207 | HTTP_MULTI_STATUS | (WebDAV; RFC 4918) The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made. |
| 208 | HTTP_ALREADY_REPORTED | (WebDAV; RFC 5842) The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again |
| 226 | HTTP_IM_USED | (RFC 3229) The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. |
| 3xx | Redirection | |
| 300 | HTTP_MULTIPLE_CHOICES | The request resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that user (or user agent) can select a preferred representation and redirect its request to that location. |
| 301 | HTTP_MOVED_PERMANENTLY | The request resource has been assigned a new permanent URI and any furture references to this resource SHOULD be done using one of the returned URIs. |
| 302 | HTTP_MOVED_TEMPORARILY | The requested resource resides temporarily under a different URI. |
| 303 | HTTP_SEE_OTHER | The response to the request can be found under a diffenent URI and SHOULD be retrieved using GET method on that resource. |
| 304 | HTTP_NOT_MODIFIED | If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this code. |
| 305 | HTTP_USE_PROXY | The requested resource MUST be accessed through the proxy given by the Location field. |
| 307 | HTTP_TEMPORARY_REDIRECT | (since HTTP/1.1) In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For instance, a POST request should be repeated using another POST request |
| 308 | HTTP_PERMANENT_REDIRECT | (RFC 7538) The request, and all future requests should be repeated using another URI. 307 and 308 parallel the behaviours of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly. |
| 4xx | Client Error | |
| 400 | HTTP_BAD_REQUEST | The request could not be understood by the server due to malformed syntax. |
| 401 | HTTP_UNAUTHORIZED | The request requires user authentication |
| 402 | HTTP_PAYMENT_REQUIRED | This code is reserved for future use. |
| 403 | HTTP_FORBIDDEN | The server understood the request, but is refusing to fulfill it. |
| 404 | HTTP_NOT_FOUND | The server has not found anything matching the Request-URI. |
| 405 | HTTP_METHOD_NOT_ALLOWED | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. |
| 406 | HTTP_NOT_ACCEPTABLE | The resource identifed by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers send in the request. |
| 407 | HTTP_PROXY_AUTHENTICATION _REQUIRED |
This code is similar to Unauthorized, but indicates that the client MUST first authenticate itself with the proxy. |
| 408 | HTTP_REQUEST_TIME_OUT | The client did not produce a request within the time that the server was prepared to wait. |
| 409 | HTTP_CONFLICT | The request could not be completed due to a conflict with the current state of the resource. |
| 410 | HTTP_GONE | The requested resource is no longer available at the server and no forwarding address is known. |
| 411 | HTTP_LENGTH_REQUIRED | The server refused to accept the request without a defined Content-Length. |
| 412 | HTTP_PRECONDITION_FAILED | The precondition given in one or more of the request-headers fields evaluated to false when it was tested on the server. |
| 413 | HTTP_REQUEST_ENTITY _TOO_LARGE |
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. |
| 414 | HTTP_REQUEST_URI_TOO_LARGE | The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. |
| 415 | HTTP_UNSUPPORTED_MEDIA_TYPE | The server is refusing to service the request because the entity of the request is in format not supported by the requested resource for the requested method. |
| 416 | HTTP_RANGE_NOT_SATISFIABLE | The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously |
| 417 | HTTP_EXPECTATION_FAILED | The server cannot meet the requirements of the Expect request-header field. |
| 418 | (RFC 2324) This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by tea pots requested to brew coffee. This HTTP status is used as an easter egg in some websites, including Google.com | |
| 421 | HTTP_MISDIRECTED_REQUEST | (RFC 7540) The request was directed at a server that is not able to produce a response (for example because a connection reuse). |
| 422 | HTTP_UNPROCESSABLE_ENTITY | (WebDAV; RFC 4918) The request was well-formed but was unable to be followed due to semantic errors. |
| 423 | HTTP_LOCKED | (WebDAV; RFC 4918) The resource that is being accessed is locked. |
| 424 | HTTP_FAILED_DEPENDENCY | (WebDAV; RFC 4918) The request failed due to failure of a previous request (e.g., a PROPPATCH) |
| 426 | HTTP_UPGRADE_REQUIRED | The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field |
| 428 | HTTP_PRECONDITION_REQUIRED | (RFC 6585) The origin server requires the request to be conditional. Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict." |
| 429 | HTTP_TOO_MANY_REQUESTS | (RFC 6585) The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes |
| 431 | HTTP_REQUEST_HEADER _FIELDS_TOO_LARGE |
(RFC 6585) The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large |
| 5xx | Server Error | |
| 500 | HTTP_INTERNAL_SERVER_ERROR | The server encountered an unexpected condition which prevented it from fulfilling the request. |
| 501 | HTTP_NOT_IMPLEMENTED | The server does not support the functionality required to fulfill the request. |
| 502 | HTTP_BAD_GATEWAY | The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
| 503 | HTTP_SERVICE_UNAVAILABLE | The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. |
| 504 | HTTP_GATEWAY_TIME_OUT | The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server it accessed in attempting to complete the request. |
| 505 | HTTP_VERSION_NOT_SUPPORTED | The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. |
| 506 | HTTP_VARIANT_ALSO_VARIES | (RFC 2295) Transparent content negotiation for the request results in a circular reference |
| 507 | HTTP_INSUFFICIENT_STORAGE | (WebDAV; RFC 4918) The server is unable to store the representation needed to complete the request. |
| 508 | HTTP_LOOP_DETECTED | (WebDAV; RFC 5842) The server detected an infinite loop while processing the request (sent in lieu of 208 Already Reported) |
| 510 | HTTP_NOT_EXTENDED | (RFC 2774) Further extensions to the request are required for the server to fulfill it. |
| 511 | HTTP_NETWORK _AUTHENTICATION_REQUIRED |
(RFC 6585) The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot) |