Status Codes

HTTP status codes are three-digit codes that can be categorized into five classes: 1xx (informational responses), 2xx (successful responses), 3xx (redirection), 4xx (client errors), and 5xx (server errors).

The following table lists the common status codes.

Status Code	Message	Description
100	Continue	The client should proceed with the request. This provisional response informs the client that part of the request has been received and has not yet been rejected by the server.
101	Switching Protocols	Switching protocols. The target protocol must be more advanced than the source protocol. For example, the current HTTPS protocol is switched to a later version.
200	OK	The server has successfully processed the request.
201	Created	The request has been fulfilled and has resulted in one or more new resources being created.
202	Accepted	The request has been accepted, but the processing has not been completed.
203	Non-Authoritative Information	Non-authoritative information. The request is successful.
204	No Content	The request has been fulfilled, but the HTTP response does not contain a response body. The status code is returned in response to an HTTP OPTIONS request.
205	Reset Content	The server has fulfilled the request, but the requester is required to reset the content.
206	Partial Content	The server has successfully processed parts of the GET request.
300	Multiple Choices	There are multiple options for the location of the requested resource. The response contains a list of resource characteristics and addresses from which a user client (such as a browser) can choose the most appropriate one.
301	Moved Permanently	The requested resource has been assigned a new permanent URI, and the new URI is contained in the response.
302	Found	The requested resource has been temporarily moved to a new location.
303	See Other	The response to the request can be found under a different URI, and should be retrieved using the GET or POST method.
304	Not Modified	The requested resource has not been modified. When the server returns this status code, it does not return any resources.
305	Use Proxy	The requested resource must be accessed through a proxy.
306	Unused	This HTTP status code is no longer used.
400	Bad Request	Invalid request. The client should not repeat the request without modifications.
401	Unauthorized	The authorization information provided by the client is incorrect or invalid.
402	Payment Required	This status code is reserved for future use.
403	Forbidden	The request has been rejected. The server understood your request but refuses to authorize it, meaning you do not have permission to access the requested resource. The client should not repeat the request without modifications.
404	Not Fou	The requested resource could not be found. The client should not repeat the request without modifications.
405	Method Not Allowed	The method received in the request is not supported by the target resource. The client should not repeat the request without modifications.
406	Not Acceptable	The server cannot fulfill the request according to the content characteristics of the request.
407	Proxy Authentication Required	The request cannot be fulfilled because the client needs to authenticate with a proxy server before accessing the desired resource. This is similar to 401.
408	Request Timeout	The server didn't receive a complete request message within the time that it was prepared to wait. The client may repeat the request without modifications at any time later.
409	Conflict	The server cannot fulfill the request due to a conflict with the current state of the resource. This status code indicates that the resource that the client attempts to create already exists, or the requested update failed due to a conflict.
410	Gone	The requested resource is no longer available. The status code indicates that the requested resource has been deleted permanently.
411	Length Required	The server refuses to process the request without a defined Content-Length.
412	Precondition Failed	The server does not meet one of the preconditions that the requester puts on the request.
413	Request Entity Too Large	The server refuses to process the request because the payload size is too large. The server may close the connection to prevent the client from continuously sending the request. If the server cannot process the request temporarily, the response will contain a Retry-After header field.
414	Request URI Too Long	The request URI is too long for the server to process.
415	Unsupported Media Type	The server is unable to process the media format in the request.
416	Requested Range Not Satisfiable	The requested range is invalid.
417	Expectation Failed	The server fails to meet the requirements of the Expect request-header field.
422	Unprocessable Entity	The request is well-formed but cannot be processed due to semantic errors.
429	Too Many Requests	The client has sent excessive number of requests to the server within a given time (exceeding the limit on the access frequency of the client), or the server has received an excessive number of requests within a given time (beyond its processing capability). In this case, the client should resend the request after the time specified in the Retry-After header of the response has elapsed.
500	Internal Server Error	The server is able to receive the request but unable to understand it.
501	Not Implemented	The server does not support the functionality required to fulfill the request.
502	Bad Gateway	The server is acting as a gateway or proxy and receives an invalid request from a remote server.
503	Service Unavailable	The requested service is invalid. The client should not repeat the request without modifications.
504	Gateway Timeout	The request cannot be fulfilled within a given time. This status code is returned to the client only when the Timeout parameter is specified in the request.
505	HTTP Version Not Supported	The server does not support the HTTPS protocol version used in the request.