My Android advanced tour ------ & gt; HTTP return Status values

When a user clicks or a search engine sends a browser request to the website server, the server returns the Http Header status code: 1. If Http/1.1 200 OK is accessed normally, the access is successful and the status of the website is normal. 2. Http/1.1 301 Moved Permanently 301 redirection permanent redirection: A relatively friendly jump Method for search engines. When a website changes its domain name, the original domain name can be Permanently redirected to the new domain name as 301, the weight of the original domain name can be transferred to a new domain name, and 301 of the domain name without www is usually redirected to a domain name with www, for example, if xxx.com redirects to www.xxx.com 3 through 301 and Http/1.1 302 Found is a temporary redirection, it is prone to search engine fraud, such as asp program response. redirect () Jump, js jump, or static http jump. 4. The Http/1.1 400 Bad Request domain name binding error is generally caused by the fact that the domain name on the server is not successfully bound or not filed for record. 5. Http/1.1 403 Forbidden has no permission to access this site. your IP address is blacklisted. There are too many connected users. You can try again later and resolve the website domain name to the space, but the space is not bound to this domain name. 6. If the Http/1.1 404 Not Found file or directory does Not exist, the requested file or directory does Not exist or is deleted. When setting the 404 error page, make sure that the returned value is 404. Generally, a 404 error page is incorrectly set, leading to a failure of 404 returned by a non-existent page, resulting in downgrading of the search engine. 7. Http/1.1 500 Internal Server Error program or Server Error indicates an Internal program Error on the Server. The following prompt appears: an Error occurs on the program page, such as a small syntax Error, data Connection faults. The so-called 404 page of the Http status code list is the page that the server returns the 404 redirection status. The number 404 indicates the status code 404. Generally, status codes 200 and 404 are commonly used. 200 indicates that the webpage is successfully downloaded, and 404 indicates that the webpage cannot be downloaded successfully and an error is generated. The following is a list of HTTP status codes. 1xx: request received, continue processing 2xx: operation successfully received, analysis, accept 3xx: complete this request must be further processed 4xx: The request contains an error syntax or cannot complete 5xx: the server fails to execute a completely valid request. 1xx indicates that the request is received and the request is processed continuously. 100 indicates that the client must continue to send the request. 101 indicates that the server is successfully received after the request is converted to the HTTP protocol version 2xx, analyze and accept 200 -- transaction success 201 -- prompt to know the URL202 of the new file -- accept and process, but not complete 203 -- return information uncertain or incomplete 204 -- Request received, however, the returned message is null. For example, if the server completes the request, the user agent must reset the file 205 that has been browsed. For example, the server has completed the GET request of some users 3xx: to complete this request, you must further process 300. The requested resource can obtain 301 in multiple locations. The request data is deleted. The request data is 302 at another address. We recommend that you access other URLs or access methods. -- The client has executed GET, but the file has not changed. 305 -- the requested resource is required. You must obtain code 306 from the address specified by the server -- the code used in the HTTP of the previous version, and no longer use 307 in the current version -- declare that the requested resource is temporarily deleted 4xx: the request contains an error syntax or cannot complete 400 -- the error request, for example, syntax error 401 -- Request Authorization failed 402 -- retain valid ChargeTo header response 403 -- Request not allowed 404 -- no file found, query, or URl405 -- the method defined by the user in the Request-Line field is not allow 406 -- drag Based on the Accept sent by the user, the requested resource cannot be accessed 407 -- similar to 401, the user must first get the authorization 408 on the proxy server -- the client did not complete the request 409 within the user's specified time-for the current resource status, request cannot be completed 410 -- the server no longer has this resource and no further reference address 411 -- the server rejects the User-Defined Content-Length attribute request 412 -- one or more request header fields in the current error 413 in request -- the requested resource is greater than the size allowed by the server 414 -- the requested resource URL is longer than the server The allowed length is 415-the request resource does not support the request project format 416-The request contains the Range request header field, and there is no range indication value within the current request resource Range, the request does not contain the If-Range request header field 417 -- the server does not meet the expectation specified by the request's Expect CT header field. If it is a proxy server, the next-level server may not meet the request 5xx: the server fails to execute a fully valid request 500 -- the server generates an internal error 501 -- the server does not support the requested function 502 -- the server is temporarily unavailable, sometimes, to prevent system overload by 503-server overload or service suspension by 504-gateway overload, the server uses another gateway or service to respond to users, long wait time setting value: 505 -- the HTTP Version specified in the request header is not supported or rejected by the server ================ ====================================================== some common statuses code: 200-the server returns the webpage 404 successfully.-The requested webpage does not exist. 503- The complete list of HTTP status codes is provided under server timeout. Click the link to learn more. You can also visit the W3C page on the HTTP status code to obtain more information. 1xx indicates the status code of the temporary response and requires the requester to continue the operation. 100 (CONTINUE) the requester shall continue to make the request. The server returns this code, indicating that the first part of the request has been received and is waiting for the remaining part. 101 (switching protocol) the requester has requested the server switching protocol. The server has confirmed and is ready to switch. 2xx indicates that the request status code is successfully processed. 200 (successful) the server has successfully processed the request. Generally, this indicates that the server provides the requested webpage. If this status code is displayed for your robots.txt file, it indicates that Googlebot has successfully retrieved the file. The 201 (created) request is successful and the server creates a new resource. 202 (accepted) the server has accepted the request but has not yet processed it. 203 (unauthorized information) the server has successfully processed the request, but the returned information may come 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 requester to reset the document view (for example, clear the form content to enter new content ). 206 (partial content) The server successfully processes some GET requests. To complete the 3xx (redirection) request, further operations are required. These status codes are usually used for redirection. Google recommends that you use redirection no more than 5 times in each request. You can use the website administrator tool to check if Googlebot encounters any problems when crawling the redirected webpage. The web capture page under diagnosis lists URLs that cannot be crawled by Googlebot due to redirection errors. 300 (multiple options) for requests, the server can perform multiple operations. The server selects an operation based on the user agent or provides an operation list for the user agent to select. The webpage of the 301 (permanent mobile) request has been permanently moved to a new location. When the server returns this response (response to a GET or HEAD request), it automatically redirects the requester to a new location. You should use this code to tell Googlebot that a webpage or website has been permanently moved to a new location. The 302 (temporary mobile) server currently responds to requests from different locations, but the requester should continue to use the original location to respond to subsequent requests. Similar to code 301 In response to GET and HEAD requests, this code automatically redirects the requester to different locations. However, you should not use this code to tell Googlebot that a webpage or website has been moved, because Googlebot will continue to capture the original location and compile the index. 303 (view other locations) when the requester uses a separate GET request for different locations to retrieve the response, the server returns this code. For all requests except HEAD, the server automatically redirects to other locations. 304 (not modified) the requested webpage has not been modified since the last request. When the server returns this response, no webpage content is returned. If the webpage has not been changed Since the last request, you should Configure the server to return this response (known as the If-Modified-Since HTTP header ). The server can tell the search engine's spider/robot that the webpage has not changed since the previous capture, thus saving bandwidth and overhead.. 305 (using a proxy) the requester can only use a proxy to access the requested webpage. If the server returns this response, it also indicates that the requester should use a proxy. 307 (temporary redirection) The server currently responds to requests from different locations, but the requester should continue to use the original location to respond to subsequent requests. Similar to code 301 In response to GET and HEAD requests, this code automatically redirects the requester to different locations. However, you should not use this code to tell Googlebot that a page or website has been moved, because Googlebot will continue to capture the original location and compile the index. 4xx (request error) status codes indicate that the request may be faulty, which hinders server processing. 400 (incorrect request) the server does not understand the request syntax. 401 (unauthorized) requests require authentication. The server may return this response for the webpage requested after logon. 403 (Forbidden) The server rejects the request. If you see this status code when Googlebot tries to capture a valid webpage on your website (you can see this information on the web capture page diagnosed by Google's website administrator tool ), it may be that your server or host rejects Googlebot access. 404 (not found) The server cannot find the requested webpage. For example, this code is often returned for webpages that do not exist on the server. If the robots.txt file does not exist on your website and you see this status code on the robots.txt page of the Google website administrator tool "Diagnostics" tab, this is the correct status code. However, if you have a robots.txt file and you see this status code, it indicates that your robots.txt file may be named incorrectly or in an incorrect location (the file should be in a top-level domain named robots.txt ). If you see this status code for the URL crawled by Googlebot (on the HTTP Error page of the "diagnosis" tab ), it indicates that Googlebot may follow the invalid link of another page (the old link or incorrect link entered ). 405 (method disabled) disable the method specified in the request. 406 (unacceptable) unable to respond to the requested webpage using the requested content features. 407 (proxy authorization required) this status code is similar to 401 (unauthorized), but the specified requester should authorize the use of the proxy. If the server returns this response, it also indicates that the requester should use a proxy. 408 (request timeout) timeout occurred when the server waited for the request. 409 conflict occurs when the server completes the request. The server must contain conflict information in the response. When the server responds to a PUT request that conflicts with the previous request, it may return this code and a list of differences between the two requests. 410 (Deleted) If the requested resource has been permanently deleted, the server returns this response. This code is similar to the 404 (not found) code, but sometimes it is used to replace the 404 code when the resource exists before and does not exist. If the resource has been moved permanently, you should use 301 to specify a new location for the resource. The 411 (valid length required) server does not accept requests that do not contain valid Content Length header fields. 412 (not meeting the prerequisites) the server does not meet one of the prerequisites set by the requester in the request. 413 (the Request Entity is too large) The server cannot process the request because the request entity is too large and exceeds the server's processing capability. 414 (the requested URI is too long) The request URI (usually the URL) is too long and cannot be processed by the server. 415 (unsupported media type) The request format is not supported by the request page. 416 (the request range does not meet the requirements) if the page cannot provide the request range, the server returns this status code. 417 (not meeting expectations) the server does not meet the "expectation" request header field requirements. The status codes 5xx (server errors) indicate an internal error when the server processes the request. These errors may be server errors rather than request errors. 500 (internal server error) The server encounters an error and cannot complete the request. 501 (not implemented) the server does not have the function to complete the request. For example, this Code may be returned when the server cannot identify the request method. The 502 (error gateway) server acts as a gateway or proxy and receives an invalid response from the upstream server. 503 (Service unavailable) servers are currently unavailable (due to overload or downtime maintenance ). Generally, this is only a temporary status. 504 (gateway timeout) The server acts as a gateway or proxy, but does not receive a request from the upstream server in time. 505 (HTTP Version Not Supported) the server does not support the HTTP protocol version used in the request.