General HTTP status Code

In the actual application of website construction, prone to a lot of small mistakes, like MySQL originally optimized not in place, affecting the overall site browsing effect, in fact, the site's regular http Status code performance is the same,

Some of the common status codes are:

$- Server successfully returned to Web page

404- The requested page does not exist

503- Server timeout

　　1xx ( Temporary response )

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

　　( continued ) The requestor 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 the status code of the request was successfully processed.

A successful Server has successfully processed the request. Typically, this indicates that the server provided the requested Web page.

　　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-authorised 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 content ) the server successfully processed some GET request.

3xx ( redirected )

Further action is required to complete the request. Typically, these status codes are used for redirection.

( multiple options ) The server can perform a variety of actions for 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 ) The requested page has been permanently moved to a new location. The server returns this response (   GET  or   HEAD  request response

302 ( temporary move ) The server is currently responding to requests from Web pages in different locations, but the requestor should continue to use the original location to respond to subsequent requests. This code is in response to   GET  and   HEAD    of the request; 301 

　　303 ( See other locations ) The requester should use a separate location for different locations GET request to retrieve the response, the server returns this code. 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 page content is not returned , and the page is usually cached for subsequent requests to display this status code.

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 that the webpage has not changed since the last crawl, thus saving bandwidth and overhead.

　　.

　　305 ( using proxies ) 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 Web pages in different locations, but the requestor should continue to use the original location to respond to subsequent requests. This code is in response to   GET  and   HEAD    of the request; 301  code similar, will automatically move the requestor to a different location, but you should not use this code to tell   googlebot  a page or site has moved because   googlebot 

　　4xx ( request error )

These status codes indicate a possible error in the request and hinder the processing of the server.

　　( error request ) the server does not understand the syntax of the request.

　　401 ( not authorized ) Request authentication required. The server may return this response for Web pages that are requested after logging in.

　　403 ( Forbidden ) The server rejected the request. If you See this status code when Googlebot tries to crawl a valid webpage on your site ( You can This information is seen on the Web crawl page under Diagnostic site administrator Tools ), and may be that your server or host has denied Googlebot access.

404 ( not found ) The requested webpage was not found by the server. For example, this code is often returned for Web pages that do not exist on the server.

　　

　　405 ( method disabled ) disables the method specified in the request.

　　406 ( not accepted ) The requested content attribute could not be used to respond to the requested Web page.

　　407 ( requires proxy authorization ) This status code is associated with 401 ( not authorized ) similar, 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 encountered a conflict while completing 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 in place of 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 ( valid length required ) the server does not accept requests that do not contain a valid Content-Length header field.

　　412 ( Prerequisites not met ) The server did 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 ) of the request URI ( usually URL ) too long, the server cannot 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 ( expectations not met ) Server not satisfied " expected " Request header field requirements.

　　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.

( 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 received 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 does not receive requests from the upstream server in a timely manner.

　　505 (HTTP version not supported ) the server does not support requests that are used in HTTP Protocol version:

General HTTP status Code