Website log http return code parsing

Website log http return code parsing
Most of the time, the traffic statistics tool does not help us to understand the website's operating status well. The emergence of website logs helps us solve this problem. Analyze the http return code of the server log and understand the current situation of Website access. long-term analysis of the HTTP status code in the website log can identify the negative details of the website, this includes understanding the time and interval when a spider starts a website, so that website administrators can better manage and optimize the website. Generally, website logs are stored in the logfiles folder of the VM. You can download the website logs by using the FTP tool, view the logs by using the txt document, or analyze the logs by using tools. Today, Xiamen seo will explain some common status codes. 200: the server returns the webpage successfully. Congratulations, you have been successfully crawled. 404: the requested webpage does not exist. Check the dead link and find dead links on those pages according to the log, then modify the code or change to 503: the server times out, which is generally caused by access failure. This may be caused by the site code or the server itself. If the code is excluded, 503 of the space is often occupied, it is best to change as soon as possible to avoid downgrading the following is the complete http return code list and related parsing: 2xx (successful) Macau Wynn Hotel URL: http://www.yongli-jiudian.com indicates that the request was successfully processed status code. 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. 1xx (temporary response) Status Code indicating a temporary response and requiring the requester to continue the operation at the Yongli Hotel in Macau, Yongli luxury resort Resort Casino in Macao, and Yongli Macao and the official website of the Wanli Macao Hotel. 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. 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. Galaxy Macau hotel website: http://www.aomenyinhejiudian.com Macau hotel, Galaxy Macau Hotel Casino Resort official website, Galaxy Macau hotel online reservation 303 (see other locations) the server returns this code when the requester uses a separate GET request to retrieve the response from different locations. 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. 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. These status codes indicate that the request may fail and impede 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 diagnosis 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 the status code is displayed 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. Football Score live video www.133bifen.com Football Score live video, 133 score live video, score live video, live video, instant score, fast score live video 406 (unacceptable) unable to use the requested content features to respond to the requested webpage. 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 the expected value) the server does not meet the "expected" request header field requirements. Website logs detail the IP address, time, operating system, browser, and resolution of the user's access to the page of your website. It can be said that he is a piece of data that every SEO person must analyze in detail, so we must remember the habit of enabling logs when making the website.