HTTP status Code

When a viewer accesses a webpage, the browser of the viewer makes a request to the server where the page is located. When a Web page is received and displayed by the browser, the server on which the page resides returns a message header (server header) that contains the HTTP status code to respond to the browser's request. HTTP status code in English is HTTP status code. The following are common HTTP status codes: 200-Request Success 301-Resources (Web pages, etc.) are permanently transferred to other URL404-the requested resource (Web page, etc.) does not exist 500-Internal server error HTTP status Code classification HTTP status code consists of three decimal digits, The first decimal number defines the type of the status code, and the latter two numbers do not have a function of classification. HTTP status code is divided into 5 types: HTTP status Code Classification classification description 1** information, the server receives the request, requires the requestor to continue the Operation 2** successful, the operation was successfully received and processed 3** redirect, need further action to complete the request 4** client error, The request contains a syntax error or an inability to complete the request 5** Server error, the server has an error while processing the request HTTP Status Code list: HTTP status Code list status code status codes English name Chinese description 100Continue continue. The client should continue its request for the 101Switching protocols switch protocol. The server switches the protocol based on the client's request. You can only switch to a more advanced protocol, for example, to switch to HTTP for a new version of the Protocol 200OK request successfully. Typically used for Get and POST request 201Created has been created. Successfully requested and created a new resource 202Accepted accepted. The request has been accepted, but the completed 203non-authoritative information non-authorized information has not been processed. The request was successful. But the meta information returned is not in the original server, but instead a copy of 204No content is nothing. The server processed successfully, but the content was not returned. Without updating the page, make sure the browser continues to display the current document 205Reset content reset. The server processing succeeds, and the user terminal (for example: browser) should reset the document view. This return code clears the contents of the 206Partial Content section of the browser's form field. The server successfully processed the partial GET request 300Multiple choices multiple options. The requested resource can include multiple locations, which can return a list of resource characteristics and addresses for the user terminal (for example: browser) to select the 301Moved permanently permanent move. The requested resource has been permanently moved to the new URI, the return information will include the new URI, and the browser will automatically redirect to the new URI. Any future new request should be replaced with a new URI 302Found temporary movement. Similar to 301. But resources are only temporarily moved. The client should continue to use the original Uri303see other to view other addresses. Similar to 301. Use Get and POST requests to view 304Not modified not modified. The requested resource is not modified and no resources are returned when the server returns this status code. Clients typically cache accessed resources by providing a header that indicates that the client wants to return only the resources that were modified after the specified date to use the proxy 305Use proxy. The requested resource must have access to the 306Unused by proxy for the temporary redirection of the HTTP status code 307Temporary redirect that has been discarded. Similar to 302. Using GET requests to redirect 400Bad request client request syntax error, the server cannot understand that 401Unauthorized requests require the user's identity authentication 402Payment required reserved, In the future, the request of the requesting client is understood using the 403Forbidden server, but the 404Not found server cannot find the resource (Web page) based on the client's request. Through this code, the website designer can set the "The resource you requested cannot be found" character page 405Method not allowed the method in the client request is forbidden 406Not acceptable the server cannot complete the request based on the content characteristics requested by the client 407Proxy Authentication Required request proxy authentication, similar to 401, but the requestor should use the proxy authorization 408Request time-out server waiting for the client to send a request too long, A time-out 409Conflict server completes a put request from a client that is likely to return this code, and the server processes the request when the resource that conflicts with the 410Gone client request already does not exist. 410 is different from 404, if the resource is now permanently deleted and can use 410 code, the site designer can specify a new location for the resource by 301 code 411Length Required server cannot process request information sent by client without Content-length 412Precondition failed client Request information Prerequisites Error 413Request entity Too Large because the requested entity is too large , the server cannot process and therefore rejects the request. To prevent successive requests from the client, the server may close the connection. If only the server is temporarily unable to process, it will contain a retry-after response information 414request-uri Too Large The URI of the request is too long (URI is usually the URL), the server cannot process the 415Unsupported media type server cannot process the request that came with the medium format 416Requested range not satisfiable the range of client requests is not valid 417Expectation Failed server cannot meet expect request header information 500Internal Server error server internal error, unable to complete request 501Not implemented server does not support requested feature, cannot complete request 502Bad Gateway acts as a server for gateways or proxies, receiving an invalid request from the remote server 503Service unavailable The server is temporarily unable to process client requests due to overloading or system maintenance. The length of the delay can be included in the server's Retry-after header information 504Gateway time-out acting as a gateway or proxy server, not in time to obtain the request from the remote server 505HTTP Version not The supported server does not support the version of the requested HTTP protocol and cannot complete processing

HTTP status Code