Common HTTP Status Codes | kitten

Http status code is the basic knowledge of web development, the interview will often appear in this aspect of the exam. 200 Welcome back, master (normal; the request has been completed.) 301 families moved (moved-the requested data has a new location and the changes are permanent.) 307 It's not here. (Re-request URL, the client automatically requests a new address) 400 don't give the strange things to others. (Error request-the request has a syntax problem or cannot satisfy the request.) 403 It's not OK here. (Prohibit-access is not required even if authorized.) 404 There is nothing here---the others are flat. (Unable to find-the server cannot find the given resource; The document does not exist.) 405 Open mode does not (resources are forbidden) 414 this ... It's too long (request-URI too long) 418 I'm a cup of tea (I'm a teapot) 500 service Maggie's broken. (Internal error-The server cannot complete the request because of an unexpected condition.) ) 503 do not ... They're not ready yet. (No service available-the server cannot process the request due to temporary overload or maintenance.) 101 Service Kei (the server will follow the customer's request to a different protocol) 100 others ...  and to ... (The initial request has been accepted and the customer should continue to send the remainder of the request.) Common HTTP status codes and their definitions

2XX success 200 normal; request completed.  201 Normal; Immediately following the POST command.  202 normal; Accepted for processing, but processing has not yet completed.  203 normal; Partial information-the information returned is only part of the message. 204 normal; No response-received request, but no information to echo.

3xx REDIRECT 301 Moved-The requested data has a new location and the change is permanent.  302 found-The requested data has a different URI temporarily.  303 See other-you can find a response to a request under another URI, and you should use the Get method to retrieve the response.  304 Not modified-the document is not modified as expected.  305 Use proxy-the requested resource must be accessed through the agent provided in the Location field. 306 unused-is no longer in use, and retains this code for future use.

Error 400 error request in 4XX client-the request has a syntax problem or cannot satisfy the request.  401 not authorized-the client is not authorized to access the data.  402 Payment required-Indicates that the billing system is valid.  403 prohibited-access is not required even with authorization.  404 Not Found-the server cannot find the given resource; The document does not exist.  407 Proxy authentication Request-The client must first use the proxy authentication itself. 415 Media type not supported-server denial of Service request because the format of the request entity is not supported.

Error 500 internal error occurred in 5XX server-the server could not complete the request because of an unexpected condition.  501 not executed-the server does not support the requested tool.  502 Error Gateway-server received an invalid response from the upstream server. 503 cannot get service-the server cannot process the request due to temporary overload or maintenance.more detailed 4xx and 5xx status codes HTTP 400-Invalid request   HTTP 401.1-not authorized: Logon failed   HTTP 401.2-not authorized: Server configuration issues cause logon failure   HTTP 401.3-ACL disable access to resources   HTTP 401.4-Not authorized: Authorization denied by filter   HTTP 401.5-not authorized: ISAPI or CGI authorization failure   HTTP 403-Prohibit access   HTTP 403-for Internet Services Manager (HTM L) Limited access to localhost  HTTP 403.1: Prohibit executable access   HTTP 403.2-No access: No Read access   HTTP 403.3-No access: No Write access   HTTP 4 03.4-No access: Request ssl  HTTP 403.5-no access: Require SSL 128  http 403.6-Prohibit access: IP address denied   HTTP 403.7-Prohibit access: Request client certificate &nbsp ; HTTP 403.8-No access: Prohibit site access   HTTP 403.9-Prohibit access: Too many connected users   HTTP 403.10-No access: Invalid configuration   HTTP 403.11-No access: Password change   HTTP 403.12-No access: Mapper Deny access   HTTP 403.13-No access: Client certificate revoked   HTTP 403.15-No access: Too many Client access Licenses   HTTP 403.16-No access: Guest User certificate untrusted or invalid   HTTP 403.17-No access: Client certificate expired or not yet in effect   HTTP 404.1-Cannot find web site   HTTP 404-Cannot find file   HTTP 405- Resource banned   HTTP 406-Unacceptable   HTTP 407-require proxy authentication   HTTP 410-Never available   HTTP 412-Prerequisite failure   HTTP 414-Request -URI too long   HTTP 500-Internal Server error   HTTP 500.100-Internal server error-ASP error   HTTP 500-11 server shutdown   HTTP 500-12 application restart   HTTP 500-13-Service The service is too busy   HTTP 500-14-Application Invalid   HTTP 500-15-does not allow request global.asa  error 501-not implemented   HTTP 502-Gateway Error

Summary form:

Status code	Status information	Meaning
100	Continue	The initial request has been accepted and the customer should continue to send the remainder of the request. (HTTP 1.1 new)
101	Switching protocols	The server converts the request to a different protocol (HTTP 1.1 new)
200	Ok	Everything is fine, and the answer document for Get and post requests follows.
201	Created	The server has created the document, and the location header gives its URL.
202	Accepted	The request has been accepted, but processing has not been completed.
203	Non-authoritative Information	The document has returned normally, but some of the answer headers may be incorrect because a copy of the document is being used (HTTP 1.1 is new).
204	No Content	The browser should continue to display the original document without a new document. This status code is useful if the user periodically refreshes the page and the servlet can determine that the user's document is new enough.
205	Reset Content	There is no new content, but the browser should reset what it displays. Used to force the browser to clear form input (HTTP 1.1 new).
206	Partial Content	The customer sent a GET request with a range header, and the server completed it (HTTP 1.1 new).
300	Multiple choices	The documents requested by the client can be found in multiple locations, which are already listed in the returned document. If the server wants to make a preference, it should be indicated in the location answer header.
301	Moved Permanently	The client requests a document elsewhere, the new URL is given in the location header, and the browser should automatically access the new URL.
60W	Found	Similar to 301, but the new URL should be considered temporary instead of permanent. Note that the corresponding state information in the HTTP1.0 is "moved temporatily". When this status code appears, the browser can automatically access the new URL, so it is a useful status code. Note that this status code can sometimes be replaced with 301. For example, if the browser incorrectly requests Http://host/~user (a trailing slash is missing), some servers return 301, and some return 302. Strictly speaking, we can only assume that the browser will automatically redirect only if the original request is get. Please see 307.
303	Other	Similar to 301/302, the difference is that if the original request was post,location headers the redirected target document specified should be fetched via get (HTTP 1.1 new).
304	Not Modified	The client has a buffered document and makes a conditional request (typically providing a if-modified-since header that indicates that the customer wants to update only a document that is newer than the specified date). The server tells the customer that the previously buffered document can continue to be used.
305	Use Proxy	The document requested by the customer should be extracted via the proxy server indicated by the location header (HTTP 1.1 new).
307	Temporary Redirect	Same as 302 (Found). Many browsers incorrectly respond to 302 responses for redirection, even if the original request is post, even if it is actually only redirected when the POST request is answered at 303. For this reason, HTTP 1.1 has been added 307 to further clear the locale code: when a 303 reply occurs, the browser can follow the redirected get and post requests, and if 307 answers, the browser can only follow the redirection of the got request. (HTTP 1.1 new)
400	Bad Request	A syntax error occurred on the request.
401	Unauthorized	The customer attempted to access a password-protected page without authorization. A www-authenticate header is included in the answer, the browser displays the user name/password dialog Accordingly, and then makes the request again after filling in the appropriate authorization header.
403	Forbidden	The resource is not available. The server understands the customer's request, but refuses to process it. This is usually caused by a permission setting on a file or directory on the server.
404	Not Found	The resource at the specified location could not be found. This is also a common answer.
60w	Method Not allowed	The request method (get, POST, head, DELETE, put, Trace, and so on) does not apply to the specified resource. (HTTP 1.1 new)
406	Not acceptable	The specified resource has been found, but its MIME type is incompatible with the customer specified in the Accpet header (HTTP 1.1 new).
407	Proxy Authentication Required	Similar to 401 indicates that the customer must first be authorized by the proxy server. (HTTP 1.1 new)
408	Request Timeout	The customer has not made any requests during the wait time that the server has allowed. Customers can repeat the same request at a later time. (HTTP 1.1 new)
409	Conflict	Usually associated with put requests. The request cannot succeed because the request and the current state of the resource are conflicting. (HTTP 1.1 new)
410	Gone	The requested document is no longer available and the server does not know which address should be redirected to. It differs from 404 in that the return of 407 indicates that the document left the specified location permanently, while 404 indicates that the document is not available because of an unknown reason. (HTTP 1.1 new)
411	Length Required	The server cannot process the request unless the customer sends a content-length header. (HTTP 1.1 new)
412	Precondition Failed	Some prerequisites specified in the request header failed (HTTP 1.1 new).
413	Request Entity Too Large	The size of the target document exceeds the size that the server is currently willing to handle. If the server considers itself able to process the request later, it should provide a Retry-after header (HTTP 1.1 new).
414	Request URI Too Long	URI is too long (HTTP 1.1 new).
416	Requested Range not satisfiable	The server does not meet the range header specified by the customer in the request. (HTTP 1.1 new)
500	Internal Server Error	The server encountered an unexpected situation and could not complete the customer's request.
501	Not implemented	The server does not support the functionality required to implement the request. For example, the customer issued a put request that the server does not support.