Protocol Introduction: HTTP 1.1 Status Code and its meaning)

100 the initial request for continue has been accepted, and the customer shall continue to send the rest of the request. (New HTTP 1.1)

101 switching protocols server converts a client-compliant request to another protocol (New in HTTP 1.1)

200 OK everything is normal, and the response document to the get and post requests follows.

The 201 created server has created a document and the location header provides its URL.

202 accepted has accepted the request, but the processing has not been completed.

203 the non-authoritative information document has been returned normally, but some response headers may be incorrect because the document is copied (New in HTTP 1.1 ).

204 NO content does not have a new document. The browser should continue to display the original document. This status code is useful if the user regularly refreshes the page and the servlet can determine that the user document is new enough.

205 there is no new content in the reset content, but the browser should reset the content displayed by it. Used to force the browser to clear the input content of the form (New in HTTP 1.1 ).

206 partial content the client sent a GET request with a range header, and the server completed it (HTTP 1.1 New ).

300 the documents requested by the multiple choices client can be found in multiple locations, which are listed in the returned documents. If the server needs to give priority, it should be specified in the location response header.

301 moved permanently the document requested by the customer is elsewhere. The new URL is provided in the location header and the browser should automatically access the new URL.

302 found is similar to 301, but the new URL should be treated as a temporary alternative, rather than permanent. Note that the corresponding status information in http1.0 is "Moved temporatily ".

When this status code appears, the browser can automatically access the new URL, so it is a very useful status code.

Note that this status code can be replaced with 301 sometimes. For example, if the browser mistakenly requests http: // host /~ If the user (with a slash missing), some servers return 301, and some return 302.

Strictly speaking, we can only assume that the browser will automatically redirect only when the original request is get. See 307.

303 see other is similar to 301/302. The difference is that if the original request is post, the redirection target document specified by the location header should be extracted through get (New in HTTP 1.1 ).

304 The not modified client has a buffered document and issued a conditional request (generally, the IF-modified-since header is provided to indicate that the customer only wants to update the document on a specified date ). The server tells the customer that the original buffer documentation can still be used.

305 the document requested by the use proxy client should be indicated by the location header

Proxy Server

Extract (New HTTP 1.1 ).

　
307 temporary redirect
It is the same as 302 (found. Many browsers mistakenly respond to the 302 response for redirection, even if the original request is post, even if it is actually only allowed when the POST request is responded to 303
To redirect. For this reason, HTTP
1.1 adds 307 to clear the region by several status codes: When a 303 response occurs, the browser can follow the redirected get and post requests; if a 307 response occurs, the browser only
Can follow the redirection to get requests. (New HTTP 1.1)

400 syntax error in bad request.

401 unauthorized the customer attempted to access the password-protected page without authorization. The response contains a WWW-Authenticate header. the browser displays the username/password dialog box accordingly, and then sends a request again after entering the appropriate authorization header.

403 Forbidden resources are unavailable. The server understands the customer's request, but rejects the request. This is usually caused by permission settings for files or directories on the server.

404 Not found cannot find the resource at the specified position. This is also a common response.

405 method not allowed request methods (get, post, Head, delete, put, Trace, etc.) are not applicable to specified resources. (New HTTP 1.1)

406 the resource specified by not acceptable has been found, but its MIME type is incompatible with the one specified by the customer in the accpet header (New in HTTP 1.1 ).

407 proxy authentication required is similar to 401, indicating that the customer must first be authorized by the proxy server. (New HTTP 1.1)

408 request timeout the client has not sent any request within the waiting time permitted by the server. The customer can repeat the same request later. (New HTTP 1.1)

409 conflict is usually related to put requests. The request cannot be successful because the request conflicts with the current status of the resource. (New HTTP 1.1)

410 the document requested by gone is no longer available, and the server does not know which address to redirect. It differs from 404 in that if 407 is returned, the document permanently leaves the specified position, and 404 indicates that the document is unavailable for unknown reasons. (New HTTP 1.1)

The 411 length required server cannot process the request unless the customer sends a Content-Length header. (New HTTP 1.1)

412 precondition some of the prerequisites specified in the failed Request Header fail (New in HTTP 1.1 ).

413 the size of the target Request Entity too large document exceeds the size that the server is willing to process. If the server thinks it can process the request later, it should provide a retry-after header (New in HTTP 1.1 ).

414 request URI Too long URI is too long (HTTP 1.1 is new ).

416 the requested range not satisfiable server cannot meet the range header specified by the customer in the request. (New HTTP 1.1)

500 the internal server error server encounters unexpected circumstances and cannot complete the customer's request.

501 The not implemented server does not support the functions required to implement the request. For example, the customer sends a put request not supported by the server.

502 when the Bad Gateway server acts as a gateway or proxy, the server returns an invalid response to access the next server to complete the request.

503 the service unavailable server fails to respond due to maintenance or overload. For example, Servlet may return 503 when the database connection pool is full. When the server returns 503, A retry-after header can be provided.

504 gateway timeout is used by a proxy or gateway server, indicating that the remote server cannot receive a response in a timely manner. (New HTTP 1.1)

505 the HTTP Version Not Supported server does not support the HTTP Version specified in the request. (New HTTP 1.1)

 

 

From: http://tech.sina.com.cn/s/s/2006-04-14/0930905833.shtml