indicates that the request has been accepted for further processing.

indicates that the requested information has multiple representations. The default action is to treat this status as a redirect and follow the contents of the Location header associated with this response.

indicates that an intermediate proxy server received a bad response from another proxy or the origin server.

indicates that the request could not be understood by the server: BadRequest is sent when no other error is applicable, or if the exact error is unknown or does not have its own error code.

indicates that the request could not be carried out because of a conflict on the server.

indicates that the client can continue with its request.

indicates that the request resulted in a new resource created before the response was sent.

indicates that an expectation given in an Expect header could not be met by the server.

indicates that the server refuses to fulfill the request.

indicates that the requested information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

indicates that an intermediate proxy server timed out while waiting for a response from another proxy or the origin server.

indicates that the requested resource is no longer available.

indicates that the requested HTTP version is not supported by the server.

indicates that a generic error has occurred on the server.

indicates that the required Content-length header is missing.

indicates that the request method (POST or GET) is not allowed on the requested resource.

indicates that the requested information has been moved to the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

indicates that the requested information has been moved to the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response.

indicates that the requested information has multiple representations. The default action is to treat this status as a redirect and follow the contents of the Location header associated with this response.

indicates that the request has been successfully processed and that the response is intentionally blank.

indicates that the returned metainformation is from a cached copy instead of the origin server and therefore may be incorrect.

indicates that the client has indicated with Accept headers that it will not accept any of the available representations of the resource.

indicates that the requested resource does not exist on the server.

indicates that the server does not support the requested function.

indicates that the client's cached copy is up to date. The contents of the resource are not transferred.

indicates that the request succeeded and that the requested information is in the response. This is the most common status code to receive.

indicates that the response is a partial response as requested by a GET request that includes a byte range.

is reserved for future use.

indicates that a condition set for this request failed, and the request cannot be carried out. Conditions are set with conditional request headers like If-Match, If-None-Match, or If-Unmodified-Since.

indicates that the requested proxy requires authentication. The Proxy-authenticate header contains the details of how to perform the authentication.

indicates that the requested information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

indicates that the request information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will also use the POST method.

automatically redirects the client to the URI specified in the Location header as the result of a POST. The request to the resource specified by the Location header will be made with a GET.

indicates that the request is too large for the server to process.

indicates that the client did not send a request within the time the server was expecting the request.

indicates that the URI is too long.

indicates that the range of data requested from the resource cannot be returned, either because the beginning of the range is before the beginning of the resource, or the end of the range is after the end of the resource.

indicates that the client should reset (not reload) the current resource.

automatically redirects the client to the URI specified in the Location header as the result of a POST. The request to the resource specified by the Location header will be made with a GET.

indicates that the server is temporarily unavailable, usually due to high load or maintenance.

indicates that the protocol version or protocol is being changed.

indicates that the request information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will also use the POST method.

indicates that the requested resource requires authentication. The WWW-Authenticate header contains the details of how to perform the authentication.

indicates that the request is an unsupported type.

is a proposed extension to the HTTP/1.1 specification that is not fully specified.

indicates that the request should use the proxy server at the URI specified in the Location header.