Shulou(Shulou.com)06/03 Report--

This article mainly introduces "what are the common HTTP return status codes". In daily operation, I believe that many people have doubts about the common HTTP return status codes. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the questions of "what are the common HTTP return status codes?" Next, please follow the editor to study!

If a request is sent to your server to display a page on your site (for example, when a user visits your page through a browser or when a Googlebot crawls a page), the server will return a HTTP status code in response to the request.

This status code provides information about the status of the request, telling Googlebot about your Web site and the requested web page.

Some common status codes include:

200-the server returned the web page successfully

404-the requested web page does not exist

503-Server is temporarily unavailable

A complete list of HTTP status codes is provided below. Click the link to learn more. You can also visit the W3C Web page on HTTP status codes for more information.

1xx (temporary response)

A status code that represents a temporary response and requires the requestor to continue with the operation.

The code says that 100 (continue) requestors should continue to make requests. The server returns this code indicating that the first part of the request has been received and is waiting for the rest. 101 (switching protocol) the requestor has asked the server to switch the protocol, and the server has confirmed and is ready to switch.

2xx (successful)

A status code that indicates that the server successfully processed the request.

The code indicates that the 200 (successful) server has successfully processed the request. Typically, this means that the server provides the requested web page. If this status is displayed for your robots.txt file, 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 (unauthorized information) the server has successfully processed the request, but the information returned may have come from another source. The 204 (no content) server successfully processed the request but did not return anything. The 205 (reset content) server successfully processed the request but did not return anything. Unlike the 204 response, this response requires the requestor to reset the document view (for example, clear the form content to enter new content). The server successfully processed some GET requests.

3xx (redirect)

Further action is required to complete the request. 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 tool to see if Googlebot is having problems crawling redirected pages. The network fetching page under diagnosis lists the URLs that cannot be crawled by Googlebot due to a redirection error.

Code description 300 (multiple selections) the server can perform a variety of operations for the request. The server can select an action based on the requester (user agent), or provide a list of actions for the requestor to choose from. The web page requested by 301 (permanent Mobile) has been permanently moved to a new location. When the server returns this response (the response to a GET or HEAD request), it automatically moves the requestor to a 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. The 302 (temporary mobile) server currently responds to requests from web pages in different locations, but the requester should continue to use the original location for future requests. This code, similar to the 301 code that responds to GET or HEAD requests, automatically redirects the requestor to a different location, but you should not use this code to tell Googlebot that a web page or website has moved, as Googlebot continues to grab and index the original location. The server returns this code when the requester should use separate GET requests for different locations to retrieve the response. For all requests except HEAD, the server automatically goes to another location. 304 (unmodified) the requested web page 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's last request, you should configure the server to return this response (called the If-Modified-Since HTTP header). Since the server can tell Googlebot that the web page has not changed since the last crawl, it can save bandwidth and overhead.

.

305 (use proxy) requestors can only use agents to access the requested web page. If the server returns this response, it also indicates that the requestor should use a proxy. The 307 (temporary redirect) server currently responds to requests from web pages in different locations, but the requester should continue to use the original location for future requests. This code, similar to the 301 code that responds to GET and HEAD requests, automatically redirects the requestor to a different location, but you should not use this code to tell Googlebot that a page or website has moved, as Googlebot continues to grab and index the original location.

4xx (request error)

These status codes indicate that the request may have gone wrong, hindering the processing of the server.

Code description 400 (error request) the server does not understand the syntax of the request. The 401 (unauthorized) request requires authentication. For web pages that need to log in, the server may return this response. The 403 (prohibited) server rejected the request. If you see that Googlebot receives this status code when trying to crawl a valid page on your site (you can see this information on the web crawl page under the diagnosis of the Google website Administration staff), your server or host may have denied Googlebot access. 404 (not found) the server could not find the requested web page. For example, if you request a web page that does not exist on the server, the server usually returns this code. If you do not have a robots.txt file on your site and you see this status on the robots.txt page of the diagnostics tab of the Google webmaster tool, then this is the correct status. However, if you have a robots.txt file and see this status, your robots.txt file may be misnamed or in the wrong location (it should be in the top-level domain, named robots.txt).

If you see this status about the URL Googlebot is trying to crawl (on the HTTP error page of the Diagnostics tab), Googlebot may be tracking an invalid link on another page (an old link or a mistyped link).

405 (disabled method) disables the method specified in the request. 406 (unacceptable) cannot respond to a requested web page with the requested content feature. 407 (Agent authorization required) this status code is similar to 401 (unauthorized), but the designated requestor should authorize the use of the agent. If the server returns this response, it also indicates the agent that the requestor should use. 408 (request timeout) the server timed out while waiting for a request. 409 (conflict) the server collided while completing the request. The server must include information about the conflict in the response. The server may return this code when responding to a PUT request that conflicts with the previous request, along with 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 is sometimes used to replace the 404 code in cases where the resource previously existed but does not exist now. If the resource has been permanently deleted, you should use 301 to specify the new location of the resource. 411 (valid length required) the server does not accept requests without valid content length header fields. 412 (prerequisites not met) the server did not meet one of the prerequisites set by the requestor in the request. 413 (the request entity is too large) the server cannot process the request because the request entity is too large to handle. 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 format of the request is not supported by the request page. 416 (request range does not meet requirements) if the page cannot provide the requested scope, the server returns this status code. 417 (did not meet expectations) the server did not meet the requirements of the expectation request header field.

5xx (server error)

These status codes indicate that an internal error occurred while the server was trying to process the request. These errors may be the fault of the server itself, not the request error.

Code description 500 (server internal error) the server encountered an error and was unable to complete the request. The 501 (not yet 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. The 502 (error gateway) server acts as a gateway or proxy and receives an invalid response from the upstream server. The 503 (service unavailable) server is currently unavailable (due to overload or downtime maintenance). Usually, this is only a temporary state. The 504 (gateway timeout) server acts as a gateway or proxy, but does not receive a request from the upstream server in time. 505 (the HTTP version is not supported) the server does not support the HTTP protocol version used in the request. At this point, the study on "what are the common HTTP return status codes" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.