[Wbia 1.3] HTTP header return status

The following content is transferred from the http://www.cnblogs.com/goodness/admin/www.sjchaxun.cn/http/, because the web page does not go, so the Google cache in the copy of the thing.

When a user clicks or a search engine sends a browser request to the website server, the server returns the HTTP header status code:

• 1. Access to HTTP/1.1 200 OK is normal
  Indicates successful access, which is the status when the website can be accessed normally.
• 2. HTTP/1.1 301 moved permanently301 redirectionPermanent redirection
  A relatively friendly jump Method for search engines. When a website changes its domain name, the original domain name can be permanently redirected to the new domain name as 301. The weight of the original domain name can be transferred to the new domain name, also, domain names without WWW are usually redirected to those with www. For example, xxx.com redirects to www.xxx.com through 301.
• 3. HTTP/1.1 302 found is a temporary redirection.
  Easy to be judged as cheating by search engines, such as ASPProgramResponse. Redirect () Jump, JS jump, or static HTTP jump.
• 4. An error occurred while binding the HTTP/1.1 400 bad request domain name.
  Generally, the domain name on the server is not bound successfully, not filed.
• 5. HTTP/1.1 403 Forbidden does not have permission to access this site
  Your IP address is blacklisted. There are too many connected users. You can try again later. The website domain name is resolved to the space, but the space is not bound to this domain name.
• 6. The HTTP/1.1 404 Not found file or directory does not exist.
  Indicates that the request file or directory does not exist or is deleted. When setting the 404 error page, make sure that the returned value is 404. Generally, a 404 error page is incorrectly set, leading to a failure of 404 returned by a non-existent page, resulting in downgrading of the search engine.
• 7. HTTP/1.1 500 internal server error program or server error
  It indicates an internal program error on the server. The following error occurs on the program page, such as a small syntax error or data connection failure.

HTTP status code list

1xx: request received, continue processing
2XX: The operation is successfully received, analyzed, and accepted.
3xx: the request must be further processed.
4xx: The request contains an error syntax or cannot be completed
5xx: the server failed to execute a fully valid request.

100 -- the customer must continue to send the request
101 -- the client requests the server to convert the HTTP protocol version according to the request

200 -- transaction successful
201 -- prompt to know the URL of the new file
202 -- accept and process, but not complete
203 -- the returned information is uncertain or incomplete
204 -- the request is received, but the returned information is null.
205 -- when the server completes the request, the user agent must reset the file that has been browsed.
206 -- the server has completed some users' GET requests

300 -- the requested resources can be obtained in multiple places
301 -- Delete request data
302 -- request data found at other addresses
303 -- we recommend that you access other URLs or access methods.
304 -- the client has executed get, but the file has not changed
305 -- the requested resource must be obtained from the address specified by the server
306 -- used in the previous HTTP VersionCode, Which is not used in the current version
307 -- declaring temporary deletion of requested resources

400 -- incorrect request, such as syntax error
401 -- authorization request failed
402 -- retain valid chargeto header response
403 -- the request is not allowed
404 -- no file, query, or URL found
405 -- the method defined in the request-line field is not allowed.
406 -- the requested resource is inaccessible due to the user's accept drag.
407 -- similar to 401, the user must first be authorized on the Proxy Server
408 -- the client did not complete the request within the specified time
409 -- the request cannot be completed due to the current resource status
410 -- this resource is no longer available on the server and there is no further reference address
411 -- the server rejects the User-Defined Content-Length attribute request
412 -- one or more request header fields are incorrect in the current request
413 -- the requested resource is larger than the size allowed by the server
414 -- the requested resource URL is longer than the length allowed by the server
415 -- the requested resource does not support the format of the requested project
416 -- The request contains the range request header field, which has no range indication value in the current request resource range.
It does not contain the IF-range request header field.
417 -- the server does not meet the expectation specified by the request's CT header field. If it is a proxy server, it may be
The first-level server cannot meet the request

500 -- Internal error occurred on the server
501 -- the server does not support the requested function
502 -- the server is temporarily unavailable, sometimes to prevent system overload
503 -- server overload or service suspension
504 -- the gateway is overloaded. The server uses another gateway or service to respond to the user. The waiting time is long.
505 -- the server does not support or reject the specified HTTP version in the Request Header

 

English version:

100: continue
101: Switching protocols
102: Processing

200: OK
201: created
202: accepted
203: Non-authoriative Information
204: NO content
205: reset content
206: Partial content
207: Multi-status

300: Multiple Choices
301: moved permanently
302: Found
303: see other
304: not modified
305: use proxy
306 :( unused)
307: Temporary redirect

400: Bad request
401: unauthorized
402: payment granted
403: forbidden
404: file not found
405: method not allowed
406: Not acceptable
407: proxy authentication required
408: request time-out
409: Conflict
410: Gone
411: length required
412: precondition failed
413: Request Entity too large
414: Request-URI Too large
415: Unsupported media type
416: Requested range not satisfiable
417: Expectation failed
422: unprocessable entity
423: Locked
424: Failed dependency

500: Internal Server Error
501: not implemented
502: Bad Gateway
503: Service unavailable
504: gateway timeout
505: HTTP Version Not Supported
507: insufficient storage

-------------------------------------------------------

Status Code 200

220.181.32.30--[02/SEP/2008: 00: 01: 23 + 0800] "Get/article/0572/72570 .shtml HTTP/1.1" 200 28361 "-" baiduspider + (+ http://www.baidu.com/search/spider.htm )"

The 200rmb in the server log successfully downloaded the 72570.shtml file using the get 网7. That is, when a user or crawler sends a browser request to the website server, the server returns an HTTP data stream containing a status code. The 200 response code is one of the status codes, indicates that the webpage has been successfully downloaded.

Status Code 301

220.181.32.30--[02/SEP/2008: 00: 01: 31 + 0800] "Get/My/view. php? Aid = 14183 HTTP/1.1 "301-"-"" baiduspider + (+ http://www.baidu.com/search/spider.htm )"

In the server log, "301" indicates that the dynamic webpage aid = 14183 is successfully redirected using the get transmission method. That is, when a user or crawler sends a browser request to the website server, the server returns an HTTP data stream containing a status code. 301 redirection is one of the status codes, indicates that the webpage is permanently transferred to another address. In practice, we can direct multiple domain names to the same web site. This is the only way that search engines can turn.

404 status code

The Status Code 404 indicates that the web page with a URL address cannot be browsed. Many times, due to the revision of the website, many old website URLs are invalid. You need to create a 404 status page to ensure that your website is smooth and can achieve a loop effect. Remember that the 404 status page must be designed separately and cannot be directly redirected back to the home page on the server side. Otherwise, the search engine crawls a large number of homepage errors and treats them as 404 pages.

An HTTP 404 error means that the webpage to which the link points does not exist, that is, the URL of the original webpage is invalid. This situation often occurs and is difficult to avoid. For example: the original URL address cannot be accessed because the webpage URL generation rules are changed, the webpage file is renamed or moved, and the import link is misspelled. When the Web server receives a similar request, A 404 status code is returned to tell the browser that the requested resource does not exist. However, no matter Apache or IIS, the default 404 error page of the Web server is very simple, dull, and unfriendly to users, and cannot provide users with the necessary information to obtain more clues, this will undoubtedly lead to the loss of users.

Therefore, many websites use custom 404 error methods to provide user experience to avoid user loss. Generally, a general approach to customizing a 404 page is to place the website quick navigation link, search box, and special services provided by the website on the page, this can effectively help users access the site and obtain the required information.

-------------------------------------------------------

100 continue
Indicates that the client should continue the request. Send back is used to notify the client that the request has been received and has not been rejected by the server.
The client should continue to send the remaining request data or the request has been completed, or ignore the return data. The server must send
The final response is after the request.

101 switching protocols
The server changes the application protocol of the current connection through the upgrade header according to the client request. The server immediately changes the protocol according to the upgrade header.
When 101 is sent back to an empty row.

Successful
======================================
200 OK
Instruct the customer service to successfully receive, parse, and accept the request.

201 created
The request has been completed and a new returned resource is created. The created resource may be a URI resource, which is usually specified in the location header. Delivery should contain an object data
It also includes resource features and location. You can use the user or user agent to select an appropriate method. The object data format is specified by the coal type, that is, the Content-Type header. Initial Server
The specified resource must be created before the 201 status code is returned. If the behavior is not immediately executed, the server should return 202.

202 accepted
The request has been accepted for processing. However, the process is not completed. The request may or may not be followed because the request may be rejected during actual execution.

203 non-authoritative information

204 NO content
The server has accepted the request and does not need to return the Entity Data. It may need to return the update information. The delivery may contain new or updated information presented by entity-headers.

205 reset content
The server has accepted the request and the user agent should reset the document view.

206 partial content
The part of the resource that the server has accepted the GET request. The request must contain a range header to indicate that the obtained range may contain if-range header information to establish a request condition.

Redirection
========================================
300 multiple choices
The requested resource meets any rendering method.

301 moved permanently
The requested resource has been assigned a new Uri.

302 found
Request temporary files of resources through different Uris.

303 see other

304 not modified
If the client has completed a qualified request and the request is allowed, but this document has not changed, the server should return a 304 status code. 304
The status code must not contain the information body. Therefore, it usually ends with the first blank line after a header field.

305 use proxy
The requested resource must be accessed through a proxy (specified by the location field. The Location Resource provides the proxy Uri.

306 unused

307 temporary redirect

Client Error
==================================
400 bad request
The server cannot understand the request information due to incorrect syntax.

401 unauthorized
If the request requires user authentication. The return request should contain a WWW-Authenticate header field to specify the permission to request resources.

402 payment required
Reserved status code

403 Forbidden
The server rejects the request.

404 not found
The server has found any resource that matches the request-Uri.

405 menthod not allowed
The request-line method is not allowed to use the specified Uri.

406 not acceptable

407 proxy authentication required

408 reqeust timeout
The client does not submit any requests within the waiting time of the server.

409 conflict

410 gone

411 length required
The server rejects the request if the Content-Length field is not defined.

412 precondition failed

413 Request Entity too large
The server rejects the request because the request data exceeds the scope that the server can process. The server may close the current connection to prevent the client from continuing the request.

414 request-URI Too Long
The server rejects the current request because the URI length exceeds the resolution range of the server.

415 unsupported media type
The server rejects the service because the request data format is not supported by the requested resource.

416 request range not satisfialbe

417 expectation failed

Server Error
==========================================
500 Internal Server Error
The server encountered an exception and blocked the execution of the current request.

501 not implemented
The server does not have an action to complete the current request.

502 Bad Gateway
Incorrect Gateway

503 service unavailable
The server cannot process the current request because the temporary file is overloaded.

504 gateway timeout

505 HTTP Version Not Supported

Common return status codes include 200 (normal), 404 (inaccessible), 500 (PHP, ASP, and aspx errors on the page), and 301 (permanent redirection), 302 (normal jump, such as JS jump, HTTP jump, ASP respone. redirect jump and normal jump sent by PHP headers ).