Common HTTP status Codes

Some common HTTP status codes are:
200– server successfully returned to Web page
404– The requested page does not exist
503– Service Not available

Common HTTP status Code Daquan

1XX (Temporary response)
A status code that represents a temporary response and requires the requestor to continue the operation.

Code description
HTTP status Code 100 (continued) The requestor should 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.
HTTP Status Code 101 (switching protocol) The requestor has asked the server to switch protocols and the server has confirmed and is ready to switch.

2XX (Success)
Represents the status code that successfully processed the request.
Code description
HTTP status Code 200 (success) The server has successfully processed the request. Typically, this indicates that the server provided the requested Web page.
HTTP status Code 201 (created) The request was successful and the server created a new resource.
HTTP Status Code 202 (accepted) the server has accepted the request but has not yet processed it.
HTTP status Code 203 (non-authoritative information) the server has successfully processed the request, but the information returned may be from another source.
HTTP status Code 204 (no content) the server successfully processed the request, but did not return any content.
HTTP status Code 205 (reset content) the server successfully processed the request, but did not return any content.
HTTP Status Code 206 (partial) The server successfully processed a partial GET request.

3XX (redirected)
Indicates that further action is required to complete the request. Typically, these status codes are used for redirection.

Code description
HTTP status Code 300 (multiple choices) for requests, the server can perform a variety of operations. The server can select an action based on the requestor (user agent) or provide a list of actions for the requestor to select.
HTTP status Code 301 (permanently moved) The requested Web page has been permanently moved to a new location. When the server returns this response (a response to a GET or HEAD request), the requestor is automatically forwarded to the new location.
HTTP Status Code 302 (temporary move) The server is currently responding to requests from different locations, but the requestor should continue to use the original location for future requests.
HTTP Status Code 303 (view other locations) The server returns this code when the requestor should use a separate GET request for the different locations to retrieve the response.
HTTP status Code 304 (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.
HTTP status Code 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.
HTTP status Code 307 (temporary redirection) 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.

4xx (Request error)
These status codes indicate a possible error in the request and hinder the processing of the server.

Code description
HTTP Status Code 400 (Error request) The server does not understand the syntax of the request.
HTTP status Code 401 (unauthorized) request authentication required. The server may return this response for pages that need to log on.
HTTP status Code 403 (forbidden) The server rejects the request.
HTTP status code 404 (not found) The requested Web page was not found by the server.
HTTP Status Code 405 (method disabled) Disables the method specified in the request.
The HTTP status Code 406 (not accepted) cannot use the requested content attribute to respond to the requested Web page.
HTTP status Code 407 (requires proxy authorization) This status code is similar to 401 (unauthorized), but specifies that the requestor should authorize the use of the proxy.
HTTP status Code 408 (Request timed out) A timeout occurred while the server was waiting for a request.
HTTP status Code 409 (conflict) The server has a conflict when it finishes the request. The server must include information about the conflict in the response.
HTTP status Code 410 (deleted) The server returns this response if the requested resource has been permanently deleted.
HTTP status Code 411 (requires valid length) The server does not accept requests that do not contain a valid Content-Length header field.
HTTP status Code 412 (Prerequisites not met) the server does not meet one of the prerequisites set by the requestor in the request.
HTTP status Code 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.
HTTP status Code 414 (the requested URI is too long) The requested URI (usually a URL) is too long for the server to process.
HTTP status Code 415 (Unsupported media type) The requested format is not supported by the requested page.
HTTP status Code 416 (request scope does not meet requirements) if the page cannot provide the requested scope, the server returns this status code.
HTTP status Code 417 (unmet expectations) the server did not meet the requirements for the "expected" Request header field.

5XX (server error)
These status codes indicate that the server has an internal error while trying to process the request. These errors may be the error of the server itself, not the request.

Code description
HTTP status Code 500 (server internal error) the server encountered an error and could not complete the request.
HTTP status Code 501 (not yet implemented) the server does not have the ability to complete the request. For example, this code may be returned when the server does not recognize the request method.
HTTP Status Code 502 (Error Gateway) The server receives an invalid response from the upstream server as a gateway or proxy.
HTTP Status Code 503 (Service Unavailable) the server is not currently available (due to overloading or downtime maintenance). Typically, this is only a temporary state.
HTTP status Code 504 (Gateway timed out) The server acts as a gateway or proxy, but does not receive requests from the upstream server in a timely manner.
HTTP status Code 505 (HTTP version not supported) the HTTP protocol version used in the request is not supported by the server.

Status Code meaning100The client should continue to send the request. This temporary response is used to inform the client that some of its requests have been received by the server and are still not rejected. The client should continue to send the remainder of the request, or ignore the response if the request has been completed. The server must send a final response to the client after the request is complete. 101The server has understood the client's request and will notify the client via a upgrade message header that a different protocol is being used to complete the request. 　　After the last empty line of the response is sent, the server switches to those protocols defined in the upgrade message header. Similar measures should be taken only when switching to a new protocol is more beneficial. For example, switching to a new HTTP version is more advantageous than an older version, or switching to a real-time, synchronized protocol to deliver resources that exploit this type of feature. 102 by WebDAV (RFC 2518The extended status code, on behalf of processing, will continue to execute. 200The request was successful, and the desired response header or data body will be returned with this response. 201 The request has been implemented, and a new resource has been established according to the request, and its URI has been returned with the location header information. If the required resources cannot be established in a timely manner, they should return'202 Accepted'. 202the server has accepted the request but has not yet processed it. As it may be rejected, the request may or may not be executed at the end. 　　In the case of asynchronous operation, there is no more convenient way to send this status code. The purpose of a response that returns a 202 status code is to allow the server to accept requests from other processes, such as a batch-based operation that executes only once a day, without having the client remain connected to the server until the batch operation is complete. Responses that accept requests for processing and return a 202 status code should include in the returned entity some information indicating the processing of the current state, as well as pointers to processing status monitors or state predictions so that the user can estimate whether the operation has completed. 203The server has successfully processed the request, but the returned entity header meta-information is not a valid set on the original server, but a copy from a local or a third party. The current information may be a subset or a superset of the original version. For example, metadata that contains resources may cause the original server to know the meta information is super. It is not necessary to use this status code, and it is appropriate only if the response does not use this status code to return a number of OK. 204the server successfully processed the request, but did not need to return any entity content, and wanted to return the updated meta information. The response may return new or updated meta information in the form of an entity header. 　　If the header information exists, it should be echoed with the requested variable. 　　If the client is a browser, then the user's browser should keep the page that sent the request without any changes in the document view, even if the new or updated meta information by specification should be applied to the document in the user's browser's active view. Because the 204 response is forbidden to contain any message bodies, it always ends with the first empty line after the message header. 205the server successfully processed the request and did not return any content. However, unlike the 204 response, a response that returns this status code requires the requestor to reset the document view. 　　The response is primarily used to accept user input and immediately resets the form so that the user can easily start another input. As with the 204 response, the response is also suppressed to contain any message bodies and ends with the first empty line after the message header. 206 The server has successfully processed a partial GET request. 　　HTTP download tools such as FlashGet or Thunderbolt are used to implement a breakpoint continuation or to decompose a large document into multiple download segments for download at the same time. 　　The request must contain the range header information to indicate the scope of content that the client expects, and may contain if-range to be used as a request condition. The response must contain the following header fields: Content-range is used to indicate the range of content returned in this response, and if Content-type is a multi-segment download for multipart/byteranges, each multipart segment should contain Conten The T-range field is used to indicate the content scope of this paragraph. 　　If the response contains Content-length, then its value must match the true number of bytes of the content range it returns. 　　Date ETag and/or content-location, if the same request should return a 200 response. 　　Expires, Cache-control, and/or Vary, if the value may be different than the value of the other response of the same variable as before. If this response request uses If-range strong cache authentication, then this response should not contain other entity headers, and if the request for this response uses If-range weak cache authentication, then this response prohibits the inclusion of other entity headers, which avoids inconsistencies between the cached entity content and the updated entity header information. 　　Otherwise, this response should contain all the entity header fields that should be returned in the 200 response. 　　If the ETag or last-modified header does not match exactly, the client cache should prevent the content returned by the 206 response from being combined with any previously cached content. Any Range and content-are not supportedthe cache of Range headers suppresses the content returned by caching 206 responses. 207 by WebDAV (RFC 2518The extended status code, which represents the following message body, will be an XML message, and may contain a series of independent response codes, depending on the number of previous child requests. 300 the requested resource has a range of available feedback information, each with its own specific address and browser-driven negotiation information. 　　The user or browser is able to choose a preferred address to redirect itself. Unless this is a HEAD request, the response should include an entity with a list of resource attributes and addresses so that the user or browser can choose the most appropriate redirect address. This entity is formatted by content-is determined by the format defined by the Type. The browser may automatically make the most appropriate choice based on the format of the response and the ability of the browser itself. 　　Of course, the RFC 2616 specification does not specify how such an automatic selection should proceed. If the server itself already has the preferred feedback option, the URI of the feedback should be indicated in the location, which the browser may use as the address for automatic redirection. In addition, this response is cacheable unless otherwise specified. 301 the requested resource has been permanently moved to a new location, and any future references to this resource should use one of several URIs returned by this response. If possible, clients that have link editing capabilities should automatically modify the requested address to the address returned from the server. 　　Unless otherwise specified, the response is cacheable. The new permanent URI should be returned in the location domain of the response. 　　Unless this is a HEAD request, the response entity should contain a hyperlink to the new URI and a short description. 　　If this is not a GET or HEAD request, the browser disables automatic redirection unless the user confirms it, because the requested condition may vary. Note: For some use http/1.0Protocol Browser, when they send a POST request to get a 301 response, the next redirect request will become a get mode. 302 The requested resource is now temporarily responding to requests from different URIs. Because such redirects are temporary, the client should continue to send subsequent requests to the original address. Only in cache-when specified in control or expires, the response is cacheable. The new temporary URI should be returned in the location domain of the response. 　　Unless this is a HEAD request, the response entity should contain a hyperlink to the new URI and a short description. 　　If this is not a GET or HEAD request, then the browser disables automatic redirection unless the user confirms it, because the requested condition may vary. Note: Although the RFC 1945 and RFC 2068 specifications do not allow the client to change the method of the request during redirection, many existing browsers treat the 302 response as a 303 response, and use GET to access the URI specified in the location, ignoring the method originally requested. Status Codes 303 and 307 are added to clarify how the server expects the client to react. 303 The response to the current request can be found on another URI, and the client should access that resource in a GET way. This method exists primarily to allow the output of the POST request that is activated by the script to redirect to a new resource. This new URI is not an alternative reference to the original resource. Meanwhile, a 303 response is forbidden to be cached. 　　Of course, a second request (redirect) may be cached. The new URI should be returned in the location domain of the response. 　　Unless this is a HEAD request, the response entity should contain a hyperlink to the new URI and a short description. Note: many http/1.1version of the previous browser does not correctly understand the 303 status. If you need to consider the interaction with these browsers, the 302 status code should be competent, because most browsers handle 302 response in the way that the above specification requires the client to handle the 303 response should be done. 304 The server should return this status code if the client sends a conditional GET request and the request has been allowed, and the contents of the document (since the last access or condition of the request) have not changed. 　　The 304 response suppresses the inclusion of the message body, so it always ends with the first empty line after the message header. The response must contain the following header information: Date, unless the server does not have a clock. 　　If a server without a clock follows these rules, then the proxy server and the client can add the Date field to the received response header (as specified in RFC 2068), and the caching mechanism will work correctly. 　　ETag and/or content-location, if the same request should return a 200 response. Expires, Cache-control, and/or vary, if the value may be different than the value of the other response of the same variable as before. 　　If this response request uses strong cache authentication, then this response should not contain other entity headers, otherwise (for example, a conditional GET request uses weak cache validation), this response prohibits the inclusion of other entity headers, which avoids inconsistencies between the cached entity content and the updated entity header information. 　　If a 304 response indicates that the current entity does not have a cache, the caching system must ignore the response and repeat the request with no restrictions. If you receive a 304 response that requires a cache entry to be updated, the cache system must update the entire entry to reflect all the values of the fields that were updated in the response. 305the requested resource must be accessed through the specified proxy. The URI information for the specified proxy is given in the location domain, and the recipient needs to send a separate request repeatedly to access the resource. 　　Only the original server can establish a 305 response. Note: There is no explicit 305 response in RFC 2068 to redirect a single request and can only be established by the original server. Ignoring these restrictions can lead to serious security consequences. 60Sin the latest version of the specification, the 306 status code is no longer in use. 307 The requested resource is now temporarily responding to requests from different URIs. Because such redirects are temporary, the client should continue to send subsequent requests to the original address. Only in cache-when specified in control or expires, the response is cacheable. The new temporary URI should be returned in the location domain of the response. Unless this is a head request, the response entity should contain a hyperlink to the new URI and a short description. 　　Because some browsers do not recognize the 307 response, you need to add the necessary information above so that users can understand and make access requests to the new URI. If this is not a GET or HEAD request, then the browser disables automatic redirection unless the user confirms it, because the requested condition may vary. 400 1, the semantic error, the current request can not be understood by the server. 　　Unless modified, the client should not submit the request repeatedly. 2, the request parameter is incorrect. 401 The current request requires user authentication. The response must contain a Www-authenticate information header for the requested resource to ask for user information. The client can repeatedly submit a request that contains the appropriate Authorization header information. If the current request already contains the Authorization certificate, the 401 response indicates that the certificate has been rejected by the server authentication. If the 401 response contains the same authentication query as the previous response, and the browser has tried at least one validation, the browser should show the user the entity information contained in the response, because the entity information may contain related diagnostic information. See RFC 2617. 402This status code is reserved for possible future requirements. 403The server has understood the request, but refuses to execute it. Unlike the 401 response, authentication does not provide any help, and the request should not be repeated. If this is not a HEAD request, and the server wants to be able to explain why the request cannot be executed, then the reason for the rejection should be described within the entity. Of course the server can also return a 404 response if it does not want the client to get any information. 404The request failed and the requested resource was not found on the server. No information can tell the user whether the situation is temporary or permanent. If the server knows the situation, it should use the 410 status code to tell the old resources because of some internal configuration mechanism problems, has been permanently unavailable, and there is no jump to the address. 404 This status code is widely used when the server does not want to reveal exactly why the request was rejected or if no other appropriate response is available. 405the request method specified in the request line cannot be used to request the appropriate resource. 　　The response must return an allow header to indicate a list of request methods that the current resource can accept. Because the Put,delete method writes to resources on the server, most Web servers do not support or do not allow the above request method under the default configuration, and 405 errors are returned for such requests. 406 The content attribute of the requested resource could not satisfy the criteria in the request header, so the response entity could not be generated. Unless this is a HEAD request, the response should return an entity that contains the most appropriate entity attributes and address lists that the user or browser can choose from. The format of the entity is determined by content-the media type defined in the type header is determined. The browser can make the best choice based on its format and ability. However, the specification does not define any criteria for making such automatic selections. 407 is similar to the 401 response, except that the client must authenticate on the proxy server. The proxy server must return a proxy-authenticate to be used for identity questioning. The client can return a Proxy-authorization message header for verification. See RFC 2617. 408The request timed out. The client does not complete a request in the time the server is waiting to be sent. The client can submit the request again at any time without making any changes. 409The request could not be completed because there was a conflict between the current state of the requested resource and the request. This code is only allowed to be used in situations where the user is considered to be able to resolve the conflict and will resubmit the new request. 　　The response should contain enough information for the user to discover the source of the conflict. Conflicts usually occur in the processing of PUT requests. For example, in a version-checking environment, where the version information that accompanies a PUT-submitted modification request for a specific resource conflicts with one of the previous (third-party) requests, the server should return a 409 error informing the user that the request could not be completed. At this point, it is likely that the response entity will contain a diff comparison between the two conflicting versions, so that the user can resubmit the new version after merging. 410 The requested resource is no longer available on the server, and there are no known forwarding addresses. Such a situation should be considered permanent. If possible, a client with link editing should remove all references to this address after obtaining the user's permission. If the server does not know or is unsure whether the condition is permanent, then the 404 status Code should be used. 　　Unless otherwise noted, the response is cacheable. 410 The purpose of the response is primarily to help the site administrator maintain the site, informing the user that the resource is no longer available, and that the server owner wants all remote connections that point to the resource to be deleted. Such events are common in time-limited and value-added services. Similarly, a 410 response is used to notify the client that a resource that was originally owned by a person is no longer available on the current server site. Of course, it is necessary to mark all resources that are permanently unavailable as'410 Gone', and whether you need to keep this tag for a long time, depends entirely on the server owner. 411 The server refuses to accept the request without defining the Content-length header. A valid content-that indicates the length of the request message body is addedafter the Length header, the client can submit the request again. 412The server failed to satisfy one or more of these when validating the prerequisites in the header field of the request. This status code allows the client to set the prerequisites in the requested meta-information (Request header field data) when acquiring the resource, to prevent the request method from being applied to resources other than what it wants. 413 the server refuses to process the current request because the size of the entity data submitted by the request exceeds the scope that the server is willing or able to handle. 　　In this case, the server can close the connection to prevent the client from continuing to send this request. If this condition is temporary, the server should return a retry-after the response header to tell the client how much time it can retry later. 414 The requested URI length exceeds the length that the server can interpret, so the server refuses to service the request. 　　This is rare, and typically includes a form submission that should use the Post method as a Get method, which causes the query string to be too long. 　　REDIRECT uri "Black Hole", for example, each redirect takes the old Uri as part of the new URI, resulting in a long URI after several redirects. The client is trying to exploit a security vulnerability in some servers to attack the server. This type of server uses a fixed-length buffer to read or manipulate the requested URI, and when the GET parameter exceeds a certain value, a buffer overflow may result, resulting in arbitrary code being executed [1]. A server that does not have such a vulnerability should return a 414 status code. 415for the currently requested method and the requested resource, the entity submitted in the request is not a supported format in the server and therefore the request is rejected. 416 If the request contains a range request header, and any data range specified in range does not coincide with the current resource's available range, and the request does not define a If-range request header, the server should return a 416 status code. If range uses a byte range, this is the case where the first byte position of all data ranges specified by the request exceeds the current resource's length. The server should also include a Content-range entity header to indicate the length of the current resource while returning a 416 status code. This response is also forbidden to use multipart/byteranges as its content-Type. 417The expected content specified in the request header Expect cannot be satisfied by the server, or the server is a proxy server, and it has obvious evidence that the contents of the Expect are not satisfied on the next node of the current route. 421The number of connections from the current client's IP address to the server exceeds the maximum range of server licenses. Typically, the IP address here refers to the client address seen from the server (such as the user's gateway or proxy server address). In this case, the calculation of the number of connections may involve more than one end user. 422The number of connections from the current client's IP address to the server exceeds the maximum range of server licenses. Typically, the IP address here refers to the client address seen from the server (such as the user's gateway or proxy server address). In this case, the calculation of the number of connections may involve more than one end user. 422 the request is well-formed, but cannot respond due to a semantic error. (RFC 4918 WebDAV) 423 Locked The current resource is locked. (RFC 4918WebDAV)424 The current request failed, such as PROPPATCH, due to an error that occurred in a previous request. (RFC 4918WebDAV)425 is defined in the WebDAV advanced collections draft, but does not appear in the WebDAV sequence set protocol (RFC 3658). 426 the client should switch to tls/1.0. (RFC 2817)449extended by Microsoft, the representative request should be retried after the appropriate action has been performed. 500The server encountered an unexpected condition that prevented it from completing the processing of the request. In general, this problem occurs when the server's code is wrong. 30wthe server does not support a feature that is required for the current request. When the server does not recognize the requested method and cannot support its request for any resource. 502An invalid response was received from the upstream server when the server acting as a gateway or agent attempted to execute the request. 503 The server is currently unable to process requests due to temporary server maintenance or overloading. This situation is temporary and will be resumed after a certain period of time. If the delay time can be estimated, then the response can include a retry-after header to indicate the delay time. If this retry-is not givenAfter information, the client should handle it in a manner that handles 500 responses. Note: The presence of a 503 status code does not mean that the server must use it when it is overloaded. Some servers simply want to deny connections to clients. 504when a server acting as a gateway or agent attempts to execute a request, it fails to receive a response from the upstream server (the server that the URI identifies, such as HTTP, FTP, LDAP), or the secondary server (such as DNS). Note: Some proxy servers return 400 or 500 errors in DNS query timeout505The server does not support or refuses to support the HTTP version used in the request. This implies that the server cannot or does not want to use the same version as the client. The response should contain an entity that describes why the version is not supported and which protocols the server supports. 506 by the Transparent Content negotiation agreement (RFC 2295)) extension, there is an internal configuration error on behalf of the server: The requested negotiation meta-resource is configured to use itself in transparent content negotiation, so it is not an appropriate focus in a negotiation process. 507 The server cannot store the content necessary to complete the request. The situation is considered to be temporary. WebDAV (RFC 4918)509The server reached the bandwidth limit. This is not an official status code, but is still widely used. 510 the policies needed to get resources are not met. (RFC 2774)

detailed 1

Status Code status information meaningContinue the initial request has been accepted and the customer should continue to send the remainder of the request. (HTTP 1. 1 new)The 101 switching protocols server translates the client's request to another protocol (HTTP 1. 1 new)200OK Everything is fine, the answer document for Get and post requests is followed. 201The Created Server has created the document, and the location header gives its URL. 202Accepted has accepted the request, but the 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 used (HTTP 1. 1 new). 204no Content does not have a new document, the browser should continue to display the original document. This status code is useful if the user refreshes the page on a regular basis and the servlet can determine that the user's document is new enough. 205 Reset content is not new, but the browser should reset what it displays. Used to force the browser to clear the form input (HTTP 1. 1 new). The 206 Partial Content client sends a GET request with a range header that the server has completed (HTTP 1. 1 new). 300multiple Choices Customer-requested documents can be found in multiple locations that are listed in the returned document. If the server wants to make a preference, it should be indicated in the location answer header. 301Moved permanently The document requested by the customer elsewhere, the new URL is given 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 replacement, not a permanent. Note that the corresponding status information in HTTP1.0 is "Moved temporatily". When the 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 used with 301 substitutions. For example, if the browser mistakenly requests http://host/~User (the 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. See 307. 303 See other is similar to 301/302, except that if the original request is Post,location header The specified redirect target document should be fetched via get (HTTP 1. 1 new). 304 Not Modified client has buffered documents and issued a conditional request (typically provided if-modified-the since header indicates that the customer only wants documents that are newer than the specified date. The server tells the customer that the original buffered document can continue to be used. 305 Use proxy The document requested by the client should be extracted from the agent server indicated by the location header (HTTP 1. 1 new). 307 Temporary Redirect and 302 (Found) are the same. Many browsers incorrectly respond to a 302 response for redirection, even if the original request is post, even though it can actually be redirected only if the answer to the POST request is 303. For this reason, HTTP 1.1 has been added in 307 to allow for more cleanup of the region in several status codes: When a 303 response occurs, the browser can follow the redirected get and post requests, and if the 307 answer, the browser can only follow the redirect to the GET request. (HTTP 1. 1 new)400Bad Request syntax error occurred. 401 Unauthorized customer attempts to access password-protected pages without authorization. A www-authenticate header is included in the answer, and the browser displays the user's name/Password dialog box, and then make a request again after filling in the appropriate authorization header. 403Forbidden resource is not available. The server understands the customer's request, but refuses to process it. This is usually caused by the permissions set on the file or directory on the server. 404not Found cannot find the resource at the specified location. This is also a common answer. The 405 method not allowed request methods (GET, POST, HEAD, DELETE, PUT, trace, etc.) do 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 client specified in the Accpet header (HTTP 1. 1 new). 407 Proxy authentication Required is similar to 401, which means that the client must be authorized by the proxy server first. (HTTP 1. 1 new)408 Request Timeout The customer has not made any requests during the waiting time of the server license. Customers can repeat the same request at a later time. (HTTP 1. 1 new)409 Conflict is usually associated with a put request. The request cannot succeed because the request conflicts with the current state of the resource. (HTTP 1. 1 new)410 Gone The requested document is no longer available, and the server does not know which address to redirect to. It differs from 404 in that returning 407 means that the document has permanently left the specified location, and 404 indicates that the document is unavailable for unknown reasons. (HTTP 1. 1 new)411 Length Required The server cannot process the request unless the client sends a content-length header. (HTTP 1. 1 new)412 Precondition Failed Some of the 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 thinks it can process the request later, it should provide a retry-after header (HTTP 1. 1 new). 414 Request Uri Too long uri (HTTP 1. 1 new). 416 requested range not satisfiable server does not meet the Range header specified by the customer in the request. (HTTP 1. 1 new)500The Internal Server Error Server encountered unexpected conditions and was unable to complete the client's request. 501the not implemented server does not support the functionality required to implement the request. For example, a customer sends a put request that is not supported by the server. 40Swhen the bad Gateway server acts as a gateway or proxy, the server returns an illegal response in order to complete the request to access the next server. 503 Service Unavailable Server failed to answer due to maintenance or heavy load. For example, a servlet might return 503 if the database connection pool is full. When the server returns 503, it can provide a retry-After header. 504 Gateway Timeout is used by a server acting as a proxy or gateway, indicating that it is not able to get answers from remote servers in a timely manner. (HTTP 1. 1 new)505 HTTP version not supported server does not support HTTP versions as specified in the request. (HTTP 1.1 new)

Detailed 2

Common HTTP status Codes