1xx: Request received, continue processing (temporary response)2xx: Successful operation received, analysis, acceptance (success)3xx: Complete this request must be further processed (redirected)4xx: Request contains an error syntax or cannot be completed (Request error)5xx: Server performs a fully valid request failure (server error)The 1xx (temporary response) represents a temporary response and requires a status code for the requester to continue the operation.      100 (continued) the requestor shall continue to make the request. The server returns this code to indicate that the first part of the request was received and is waiting for the remainder.     101 (switching protocol) requester has requested the server to switch protocols, the server has confirmed and is ready to switch. 2xx (Success) indicates that the server successfully processed the requested status code.      200 (Success) The server has successfully processed the request. 201 (created) the request was successful and the server created a new resource. 202 (accepted) the server has accepted the request but has not yet processed it.     203 (not authorized information) the server has successfully processed the request, but the information returned may be from another source. 204 (no content) the server successfully processed the request, but did not return any content. 205 (reset content) The server successfully processed the request, but did not return any content. Unlike the 204 response, this response requires the requestor to reset the document view (for example, to clear the form contents to enter new content). 206 (partial content) &NBThe sp; server successfully processed a partial GET request. 3xx (redirected) to complete the request, further action is required. Typically, these status codes are used for redirection. Google recommends that you use redirects in each request not to exceed 5 times. 300 (multiple choices) for requests, the server can perform a variety of operations. The server can select an action based on the requestor (user agent) or provide a list of actions for the requestor to select. 301 (permanently moved) requested page has been permanently moved to a new location. When the server returns this response (response to GET or HEAD request), the requestor is automatically forwarded to the new location. You should use this code to tell Googlebot a Web page or Web site has been permanently moved to a new location. 302 (temporarily moved) server currently responds to requests from different locations, but the requestor should continue to use the original location for future requests. This code with the response GET or HEAD the 301 code of the request is similar, will automatically move the requestor to a different location, but you should not use this code to tell Googlebot a webpage or site has moved, because Googlebot will continue to crawl the original location and index it. 303 (View other locations) The requester should use a separate GET request for different locations to retrieve the response when the server returns this code. for all requests except HEAD , the server automatically goes to a different location. 304 (not modified) The requested webpage has not been modified since the last request. When the server returns this response, the Web page content is not returned. If the page has not changed since the requestor last requested it , You should configure the server to return this response (called if-modified-since HTTP header). Because the server can tell Googlebot the webpage has not changed since the last crawl, thus save bandwidth and overhead 305 (using proxies) requesters can only use proxies to access requested Web pages. If the server returns this response, it also indicates that the requestor should use the proxy. 307 (Temporary redirect) service The server is currently responding to requests from different locations, but the requestor should continue to use the original location for future requests. This code is similar to the 301 code for response GET and HEAD requests, will automatically transfer the requestor to a different location, but you should not use this code to tell Googlebot a page or site has moved, because googlebot will continue to crawl the original location and index it.  4XX (Request error) These status codes indicate a possible error in the request and hinder the processing of the server. 400 (Bad Request) server does not understand the syntax of the request.     401 (not authorized) request authentication required. The server may return this response for pages that need to log on. 403 (Forbidden) server denied request. 404 (not found) the server could not find the requested webpage. 405 (Disabled method) disables the method specified in the request. 406 (unacceptable) unable to respond to the requested Web page using the requested content attribute. 407 (requires proxy authorization) This status code is similar to 401 (unauthorized), but specifies that the requestor should authorize the use of the proxy. If the server returns this response, it also indicates which proxy the requestor should use. 408 (Request timed out) timeout occurs when the server waits for a request. 409 (conflict) The server has a conflict when the request is completed. The server must contain information about the conflict in the response. The server may return this code in response to a PUT request that conflicts with a previous request, along with a list of the two requested differences. 410 (Deleted) The server returns this response if the requested resource has been permanently deleted. This code is similar to the 404 (not found) code, but if the resource existed before and now does not exist, there are will be used to replace 404 code. If a resource has been permanently deleted, you should use 301 to specify a new location for the resource. 411 (requires valid length) server does not accept requests that do not contain valid Content-Length header fields. 412 (Not satisfiedPrerequisites) The server does not meet one of the prerequisites set by the requestor in the request. 413 (Request entity too Large) The server cannot process the request because the request entity is too large to exceed the processing power of the server. 414 (requested URI too long) requested uri (usually URL) is too long for the server to process. 415 (Unsupported media type) requested format is not supported by the requested page. 416 (Request scope not required) if the page cannot provide the requested range, the server returns this status code.     417 (not meeting expectations) server does not meet the requirements for the "expected" Request header field. 5xx (server error) These status codes indicate that the server has an internal error while trying to process the request. These errors can be errors on the server itself, not the request.      500 (Server internal error) the server encountered an error and could not complete the request.     501 (not implemented) server does not have the ability to complete the request. For example, this code may be returned when the server does not recognize the request method. 502 (Bad Gateway) server acts as a gateway or proxy and receives an invalid response from the upstream server. 503 (Service Unavailable) server is currently unable to make(due to overloading or downtime maintenance). Usually, this is only a temporary state. 504 (Gateway Timeout) server acts as a gateway or proxy, However, the request was not received in time from the upstream server. 505 (http version not supported) the server does not support the HTTP protocol version used in the request.
Various types of HTTP return status codes in a detailed
