when the user clicks or the search engine sends a browse request to the website server, the server will return HTTP header message status code, several common:1, http/1.1 OK access to normal indicates a successful access for the site when the status of normal access. 2, http/1.1 301 Moved Permanently 301 redirect Permanent redirect relatively friendly to the search engine, when the site changes the domain name can be the original domain 301 permanent redirect to the new domain name, the original domain weight can be passed to the new domain name, Also often will not contain the WWW domain name 301 jump to include www, such as xxx.com through 301 jump to Www.xxx.com 3, http/1.1 302 Found for temporary redirection easy to be search engine to be convicted of cheating, such as the response of ASP program. Redirect () jump, JS jump or static HTTP jump. 4, http/1.1-bad Request domain name binding error is generally the server domain name is not tied successfully, not the record and so on. 5, http/1.1 403 Forbidden do not have access to this station your IP is blacklisted, too many users to connect, you can try again later, the site domain name resolution to the space, but the space is not binding this domain name and so on. 6, http/1.1 404 Not Found file or directory does not exist indicates request file, directory does not exist or is deleted, set 404 error page to ensure the return value is 404. Often because the 404 error page incorrectly set causes the non-existent page to return is not 404 and causes the search engine to drop the right. 7, http/1.1, Internal Server error programs or server errors indicates server internal program errors, such a prompt is usually a program page error, such as small syntax errors, data connection failure. http Status Code list The so-called 404 page is the server 404 redirect Status return page. The number 404 refers to the number No. 404 status Code. Commonly used to have No. 200 number status code and NO. 404 number status code. Number No. 200 indicates that the Web page was downloaded successfully, while number No. 404 indicates that it cannot be downloaded successfully and generates an error. The following is a list of HTTP status codes. 1XX: Request received, continue processing 2xx: Operation received successfully, analysis, accept 3xx: Completion of this request must be further processed 4xx: The request contains an error syntax or cannot be completed 5xx: The server executed a fully valid request failed  1XX: Request received, continue processing 100-- The customer must continue to make the request 101--the client requests that the server convert the HTTP protocol version on request 2xx: Operation successfully received, analysis, accept 200--Transaction successful 201--prompt to know the new file url202--accept and process, but processing incomplete 203--return information is not determined or incomplete 204--request received, but the return information is empty 205--the server completed the request, The user agent must reset the currently browsed file 206--server has completed a partial user GET request 3xx: Completing this request must further process 300--requested resource can get 301--delete request data in multiple locations 302--found request data at other addresses 303 --The client is advised to access other URLs or Access methods 304--clients have performed a get, but the file has not changed 305--the requested resource must be obtained from the address specified by the server 306--the previous version of the code used in HTTP, the current version is no longer using the 307--claims request for temporary deletion of resources  4XX: request contains an error syntax or cannot complete 400--error request, such as syntax error 401--request authorization failed 402--reserved valid Chargeto header response 403--request does not allow 404--no discovery file, query, or url405-- The method defined by the user in the Request-line field does not allow 406--to request the resource to be inaccessible based on the accept drag sent by the user 407--similar to 401, the user must first be authorized on the proxy server 408--the client does not complete the request within the user-specified time of starvation 409-- The request cannot be completed on the current resource state 410--the server no longer has this resource and no further reference address 411--the server rejects the user-defined Content-length property request 412--One or more request header fields in the current request error 413-- The requested resource is greater than the size allowed by the server 414--the requested resource URL is longer than the length of the server allowed 415--the request resource does not support the request item format 416--The request contains a range request header field that does not have a range indication value within the current request resource scope. The request also does not contain the If-range request header field 417--The server does not meet the expected value specified by the request Expect header field, and if it is a proxy server, the next level of server may not satisfy the request 5xx: The server failed to perform a fully valid request 500-- Server generates internal error 501--server does not support requested function 502--Server is temporarily unavailable, sometimes to prevent system overload 503--server overload or pause repair 504--pass overload, Server uses another gateway or service to respond to users, waiting time setting value is longer 505-- The server does not support or deny the HTTP version specified in the request header ======================================================= Some common status codes are: 200-Server successfully returned on page 404-requested page does not exist 503-server timeout below provides a complete list of HTTP status codes 。 Click on the link to learn more. You can also get more information by accessing the pages on the HTTP status code. 1XX (ad hoc response) represents a temporary response and requires a status code for the requestor to continue to perform the operation. 100 (continued) The requesting person 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) The requestor has asked the server to switch protocols, and the server has confirmed and is ready to switch. 2XX (Success) indicates that the requested status code was successfully processed. 200 (success) The server has successfully processed the request. Typically, this indicates that the server provided the requested Web page. If this status code is displayed for your robots.txt file, it means that Googlebot has successfully retrieved the file. 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 (non-authoritative 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) The 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 no more than 5 times per request. You can use the Webmaster tools to see if Googlebot is having trouble crawling the redirected pages. The network crawl page under diagnosis lists URLs that Googlebot cannot crawl due to redirection errors. 300 (multiple options) 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) The requested page has been permanently moved to a new location. When the server returns this response (a response to a GET or HEAD request), the requestor is automatically forwarded to the new location. You should use this code to tell Googlebot that a Web page or Web site has been permanently moved to a new location. 302 (Temporary move) the server is currently from a different locationThe Web page responds to the request, but the requester should continue to use the original location to respond to subsequent requests. This code, similar to the 301 code that responds to the GET and HEAD requests, automatically transfers the requestor to a different location, but you should not use this code to tell Googlebot that a Web page or site has moved because Googlebot continues to crawl the original location and index it. 303 (View other locations) The server returns this code when the requestor should use a separate GET request for the different locations to retrieve the response. 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 (known as the If-modified-since HTTP header). The server can tell the search engine that the spider/bot has not changed since the last crawl, thus saving bandwidth and overhead. 305 (using a proxy) the requestor can only use the proxy to access the requested Web page. If the server returns this response, it also indicates that the requestor should use the proxy. 307 (Temporary redirect) The server is currently responding to requests from a Web page in a different location, but the requestor should continue to use the original location to respond to subsequent requests. This code, similar to the 301 code that responds to the GET and HEAD requests, automatically transfers the requestor to a different location, but you should not use this code to tell Googlebot that a page or site has moved because Googlebot continues 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 (Error request) The server does not understand the syntax of the request. 401 (unauthorized) request authentication is required. The server may return this response for Web pages that are requested after logging in. 403 (Forbidden) The server rejects the request. If you see this status code when Googlebot tries to crawl a valid webpage on your site (you can see this information on the Web crawl page under Google Webmaster Tools Diagnostics), your server or host may have denied Googlebot access. 404 (not found) The requested Web page was not found by the server. For example, this code is often returned for Web pages that do not exist on the server. If you do not have a robots.txt file on your site and you see this status code on the robots.txt page of the Google Webmaster Tools Diagnostics tab, this is the correct status code. However, if you have a robots.txt file and you see this status code, your robots.txt file may be named incorrectlyError or in the wrong location (the file should be in the top-level domain named robots.txt). If you see this status code for Googlebot crawled URLs (on the HTTP error page of the Diagnostics tab), it means that Googlebot follows a potentially invalid link to another page (an old link or an incorrectly entered link). 405 (method Disabled) Disables the method specified in the request. 406 (not accepted) cannot use the requested content attribute to respond to the requested Web page. 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 that the requestor should use the proxy. 408 (Request timed out) A timeout occurred while the server was waiting for a request. 409 (conflict) The server has a conflict when it finishes the request. The server must include information about the conflict in the response. This code may be returned by the server in response to a PUT request that conflicts with the previous request, as well as a list of differences of 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 is sometimes used to replace the 404 code in cases where the resource existed before and now does not exist. If the resource has been permanently moved, you should use 301 to specify a new location for the resource. 411 (requires valid length) The server does not accept requests that do not contain a valid Content-Length header field. 412 (precondition not met) 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 (The requested URI is too long) The requested URI (usually the URL) is too long for the server to process. 415 (Unsupported media type) The requested format is not supported by the requested page. 416 (Request scope does not meet the requirements) if the page cannot provide the requested range, the server returns this status code. 417 (unmet expectations) the server does not meet the requirements for the expected Request header field. 5XX (server error) These status codes indicate that an internal error occurred while the server was processing the request. These errors may be the error of the server itself, not the request. 500 (server internal error) the server encountered an error and could not complete the request. 501 (not yet implemented) the server does not have the capability to complete the request. For example, this code may be returned when the server does not recognize the request method. 502 (Error Gateway) The server receives an invalid response from the upstream server as a gateway or proxy. 503 (Service Unavailable) the server is not currently available (due to overloading or downtime maintenance). Typically, this is only a temporary state. 504 (Gateway Timeout) The server acts as a gateway or proxy, but is not received in time from the upstream serverRequest. 505 (HTTP version not supported) the HTTP protocol version used in the request is not supported by the server.
HTTP return status value detailed
