Http status code and status code

Http status code and status code

HTTP is a Request/Response network transmission protocol. When a Web page information or resource (Document) is required by a client application (browser, the website server returns the Status Code, which is usually displayed in data mode. The most common Status Code is 404, others include 200, 301, 302, 304, 403, 410, and 500.

The HTTP Status Code is in English.

The following are common HTTP status codes:

200-the request is successful. It is generally used for GET and POST requests.

301-permanent movement. The requested resource has been permanently moved to the new URI. The returned information will include the new URI, And the browser will automatically redirect to the new URI.

In the future, any new request should be replaced by a new URI.

302-temporary movement. It is similar to 301. However, resources are temporarily moved. The client should continue to use the original URI

404-the requested resource (webpage, etc.) does not exist

500-an internal server error occurs.

HTTP status code category

The HTTP status code consists of three decimal digits. The first decimal digit defines the status code type, and the last two digits do not have a classification function. There are five types of HTTP status codes:

HTTP status code category

Category	Category Description
1 **	Information, the server receives the request, the requester needs to continue the operation
2 **	Operation received and processed
3 **	Redirection. Further operations are required to complete the request.
4 **	Client error. The request contains a syntax error or the request cannot be completed.
5 **	A server error occurs when the server processes the request.

HTTP status code list

 

HTTP status code list

Status Code	English name of Status Code	Description
100	Continue	Continue. The client should continue its request
101	Switching Protocols	Switch protocol. The server switches the protocol according to the client request. You can only switch to a more advanced protocol, for example, to a new HTTP protocol.
200	OK	The request is successful. It is generally used for GET and POST requests.
201	Created	Created. The request is successful and a new resource is created.
202	Accepted	Accepted. Request accepted but not processed
203	Non-Authoritative Information	Unauthorized information. The request is successful. However, the returned meta information is not on the original server, but a copy.
204	No Content	NO content. The server successfully processes the request, but no content is returned. When the webpage is not updated, make sure that the current document is displayed in the browser.
205	Reset Content	Reset content. After the server is successfully processed, the user terminal (for example, a browser) should reset the document view. You can use this return code to clear the form field of the browser.
206	Partial Content	Some content. The server successfully processes some GET requests.
300	Multiple Choices	Multiple options. The requested resource can contain multiple locations, and a list of resource features and addresses can be returned for user terminals (for example, browsers) to select
301	Moved Permanently	Move permanently. The requested resource has been permanently moved to the new URI. The returned information will include the new URI, And the browser will automatically redirect to the new URI. In the future, any new request should be replaced by a new URI.
302	Found	Temporarily move. It is similar to 301. However, resources are temporarily moved. The client should continue to use the original URI
303	See Other	View other addresses. It is similar to 301. Use GET and POST requests to view
304	Not Modified	Not modified. The requested resource is not modified. When the server returns this status code, no resources are returned. The client usually caches the accessed resources and provides a header to indicate that the client only wants to return the resources modified after the specified date.
305	Use Proxy	Use a proxy. The requested resource must be accessed through a proxy.
306	Unused	Discarded HTTP status code
307	Temporary Redirect	Temporary redirection. It is similar to 302. Use GET request redirection
400	Bad Request	The syntax of the client request is incorrect and cannot be understood by the server.
401	Unauthorized	The request requires the user's identity authentication.
402	Payment Required	Reserved for future use
403	Forbidden	The server understands the request from the client but rejects the request.
404	Not Found	The server cannot find resources (web pages) based on client requests ). With this code, website designers can set the personalized page "the resources you requested cannot be found"
405	Method Not Allowed	The method in the client request is forbidden.
406	Not Acceptable	The server cannot complete the request based on the Content Characteristics of the client request.
407	Proxy Authentication Required	The request requires proxy authentication, similar to 401, but the requester should use the proxy for authorization
408	Request Time-out	The request sent by the server to the client is too long and times out.
409	Conflict	This code may be returned when the server completes the PUT request of the client. A conflict occurs when the server processes the request.
410	Gone	The resource requested by the client does not exist. 410 different from 404. If a resource has been permanently deleted before, you can use code 410. website designers can use code 301 to specify a new resource location.
411	Length Required	The server cannot process the request information sent by the client without Content-Length.
412	Precondition Failed	The prerequisites for client request information are incorrect.
413	Request Entity Too Large	The request is rejected because the request entity is too large and cannot be processed by the server. To prevent consecutive requests from the client, the server may close the connection. If the server cannot process the request, it will contain a Retry-After response.
414	Request-URI Too Large	The request URI is too long (the URI is usually a URL) and cannot be processed by the server.
415	Unsupported Media Type	The server cannot process the media format attached to the request
416	Requested range not satisfiable	The range of client requests is invalid.
417	Expectation Failed	The server cannot meet the response CT request header information
500	Internal Server Error	The request cannot be completed due to an internal server error.
501	Not Implemented	The server does not support the request function and cannot complete the request.
502	Bad Gateway	A gateway or proxy server receives an invalid request from the remote server.
503	Service Unavailable	The server cannot process client requests temporarily due to overload or system maintenance. The delay length can be included in the Retry-After header of the server.
504	Gateway Time-out	The server that acts as a gateway or proxy does not get requests from the remote server in time
505	HTTP Version not supported	The server cannot complete the processing because it does not support the HTTP protocol version of the request.