Ultra-verbose HTTP status Code Daquan

Ultra -Full-ultra-detailed HTTP Status Code Daquan

The remainder of this section will describe in detail the status code in the HTTP 1.1. These status codes are divided into five main categories:

The 100-199 is used to specify certain actions that the client should have accordingly.

The 200-299 is used to indicate a successful request.

300-399 is used for files that have been moved and is often included in the locator header information to specify new address information.

400-499 is used to indicate client-side errors.

500-599 is used to support server errors.

Some of the common status codes are:

- Server successfully returned to Web page

404 – The requested page does not exist

503 – The server is temporarily unavailable

The following provides a complete list of HTTP status codes.

1XX(Temporary response)

A status code that represents a temporary response and requires the requestor to perform an action before continuing.

Code Description

(continued | Continue) The requestor should continue to make the request. The return of this code by the server means that the server has received the first part of the request and is now waiting to receive the remainder.

101(Switching protocol | Switchingprotocols) The requestor has asked the server to switch protocols and the server has confirmed and is ready to switch.

2xx(Success)

The status code used to indicate that the server has successfully processed the request.

Code Description

(Success | OK) The server has successfully processed the request. Typically, this indicates that the server provided the requested Web page. If your robots.txt file is displayed for this status, this means that Googlebot has successfully retrieved the file.

201(Created | Created) The request was successful and the server has created a new resource.

202(Accepted | Accepted) The server has accepted the request, but it has not yet been processed.

203(Non-authorised information | Non-authoritativeinformation) The server successfully processed the request, but returned information that might have come from another source.

204(No content | No content) The server successfully processed the request, but did not return anything.

The 205(reset content ) 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 | Partial Content) Server successfully processed some GET requests.

3xx(redirected)

to complete the request, you need to proceed further. Typically, these status codes are always redirected. Google recommends that you use less than 5 redirects per request . You can use the Webmaster tools to see if Googlebot is having problems crawling your redirected pages. The crawl error page under diagnostics lists the URLs that Googlebot cannot crawl due to redirection errors.

Code Description

(Multiple Options | Multiplechoices) The server can perform a variety of actions based on the request. The server can select an action based on the requestor (user agent) or provide a list of actions for the requestor to select.

301 (Permanent move | Movedpermanently)   The requested page has been permanently moved to a new location. The server returns this response (as for GET HEAD request response) when The requestor is automatically forwarded to the new location. You should use this code to notify Googlebot

302 (Find | Found) The server is currently responding to requests from different locations of Web pages, However, the requester should continue to use the original location for future requests. This code responds to the GET HEAD request 301 Googlebot 302 means the message is temporarily moved (Moved temporarily)

303(see other Information | See other) This status code is similar to 301,302 , except if the initial request is POST, then the new document (given in the locator header information) is medicinal get Back. This status code is newly added to the HTTP 1.1.

304(not modified | 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 that the webpage has not changed since the last crawl, it saves bandwidth and overhead.

305(using proxies | Use proxy) The requestor can only access the requested Web page by using the delegate. If the server returns this response, the server also indicates which proxy the requestor should use.

307(Temporary redirect | Temporaryredirect) 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 for future requests. This code , like the 301 code that responds to the GET and HEAD requests , automatically transfers the requestor to a different location. However, since Googlebot will continue to crawl the original location and index it, you should not use this code to notify Googlebot that a page or site has been moved.

4xx(Request error)

These status codes indicate that the request may have failed and that the server has been prevented from processing the request.

Code Description

(Error Request | Bad Request) The server does not understand the requested syntax.

401( unauthorized | Unauthorized) requests that authentication be requested. After logging in, the server may return this response to the page.

403(Forbidden | Forbidden) The server rejects the request. If This status code appears when Googlebot tries to crawl a valid webpage on your site (you can see this status code on the Web crawl page in the Google Webmaster Tools diagnostics), then this could be your server or host rejecting Googlebot access to it.

404(not found | Not Found) The requested Web page was not found by the server. For example, if the request is for a webpage that does not exist on the server, the server typically returns this code.

If you do not have a robots.txt file on your site and you find this status on the robots.txt page of the Google Webmaster Tools Diagnostics tab, This is the correct state. However, if you have a robots.txt file and you find this status, this means that your robots.txt file may be named incorrectly or in the wrong location. (the file should be located on the top-level domain name and should be named robots.txt).

If you are Googlebot This status is found on the URL you are trying to crawl ( on the HTTP error page of the "Diagnostics" tab ), then this means Googlebot You may be tracking an invalid link (old link or incorrect input link) on another page.

405(method disabled | Method notallowed) disables the methods specified in the request.

406(not accepted | Not acceptable) cannot use the requested content attribute to respond to the requested Web page.

407(Requires proxy authorization | Proxyauthentication Required) This status code issimilar to 401 (unauthorized), but specifies that the requestor should use the proxy for authorization. If the server returns this response, the server also indicates which proxy the requestor should use.

408(Request timed out | Request Timeout) The server timed out while waiting for requests.

409(Conflict | Conflict) The server encountered a conflict while completing the request. The server must contain information about the conflicts that occurred in the response. The server may return this code in response to a PUT request that conflicts with the previous request , and will provide a list of differences for two requests.

410(Deleted | Gone) If the requested resource has been permanently deleted, the server returns this response. This code issimilar to the 404 (not Found) code, but sometimes replaces the 404 code if the resource has previously existed but now no longer exists . If the resource has been permanently deleted, you should use the 301 code to specify a new location for the resource.

411(Requires effective length | lengthrequired) The server does not accept requests that contain invalid content-Length header fields.

412(Prerequisites not met | (preconditionfailed) server does not meet one of the prerequisites set by the requestor in the request.

413(Request entity too large | Requestentity 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 | RequestUri Too long) The requested URI(usually the URL) is too long for the server to process.

415(Unsupported media type | Unsupportedmedia Type) The requested format is not supported by the requested page.

416(Request scope does not meet requirements | Requestedrange not satisfiable) If the request is made against an invalid range of pages, the server returns this status code.

417(Expectations not met | expectationfailed) 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 trying to process the request. These errors may be the error of the server itself, not the request.

Code Description

$(Server internal Error | Internalserver error) The server encountered a failure and could not complete the request.

501(not yet implemented | Not implemented) The server does not have the capability to complete the request. For example, the server may return this code when the server does not recognize the request method.

502(Error Gateway | Bad Gateway) The server received an invalid response from the upstream server as a gateway or proxy.

503(Service Unavailable | Service Unavailable) is currently unable to use the server (due to overloading or downtime maintenance). Usually, this is just a temporary state.

504(Gateway Timeout | Gateway Timeout) The server has not received the request from the upstream server as a gateways or proxy.

505(HTTP version not supported | Httpversion not supported) Server does not support the HTTP protocol version used in the request

This article is from the "Savage Power" blog, please be sure to keep this source http://chenfei123.blog.51cto.com/1427669/1703078

Ultra-verbose HTTP status Code Daquan