A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses. https://tools.ietf.org/html/rfc1945. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. Wikipedia Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. http://orgias.org/http-status/http-600-error-code.html
The server MUST send a final response after the request has been completed. Note: previous versions of this specification recommended a maximum of five redirections. If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional. General error when fulfilling the request would cause an invalid state. https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot). Unofficial codes The following codes are not specified by any RFC, but are used by third-party services to provide semantic or RESTful error responses: 103 Checkpoint Used in the resumable requests proposal to resume aborted PUT or POST requests. 420 Method Failure (Spring Framework) A deprecated response used by the Spring Framework when a method has failed. 419 I'm a fox (Smoothwall/Foxwall) Returned by some versions of Smoothwall and Foxwall firewall systems when a config test is returned. 420 Enhance Your Calm (Twitter) Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the 429 Too Many Requests response code instead. 450 Blocked by Windows Parental Controls (Microsoft) A Microsoft extension. The server should send back all the information necessary for the client to issue an extended request. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. httpstatus. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions. 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Http Code 302 The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum.
Retrieved 16 October 2015. ^ Fisher, Tim. "502 Bad Gateway". Http Response Example It's silent and doesn't warn the user about anything. 205 Reset Content This allows the server to reset any content returned by a CGI. 206 Partial Content The requested file wasn't downloaded entirely. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a redirect with a separate GET message. 304 Not Modified (RFC 7232) Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html The response representation SHOULD contain a link to a resource that allows the user to submit credentials (e.g.
Retrieved October 24, 2009. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4". Http Code 403 Retrieved 16 October 2015. ^ "Twitter Error Codes & Responses". Transparent Content Negotiation in HTTP. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response. 204 No Content The server successfully processed the request and is not returning any content. 205 Reset Content The server successfully processed the request, but is not returning any content.
Retrieved 16 October 2015. ^ Kowser; Patel, Amit. "REST response code for invalid data". Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. Http Status Code 400 The set presented MAY be a subset or superset of the original version. Http Status Codes Cheat Sheet Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
Stack Overflow. http://orgias.org/http-status/http-error-code-203.html March 2015. Retrieved 16 October 2015. ^ "408". For up-to-date details on the HTTP specification, see the latest HTTP/1.1 drafts Status codes The values of the numeric status code to HTTP requests are as follows. Http 422
If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. Http 404 Microsoft. ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers.
This condition is expected to be considered permanent. nginx 1.9.5 source code. The client should retry the request with a suitable Authorization header. Http 502 The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client. 10.3.4 303 See Other The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource.
Wikipedia The server does not meet one of the preconditions that the requester put on the request. 413 Request Entity Too Large The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The client MAY repeat the request with a suitable Authorization header field (section 14.8). The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. check over here Partial Information 203 When received in the response to a GET command, this indicates that the returned metainformation is not a definitive set of the object from a server with a copy of the object, but is from a private overlaid web.
a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response. 204 No Content The server successfully processed the request and is not returning any content. 205 Reset Content The server successfully processed the request, but is not returning any content. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Wikipedia Indicates multiple options for the resource that the client may follow. The Location field gives the URI of the proxy.
The client SHOULD NOT repeat the request without modifications. Successful creation occurred (via either POST or PUT). Retrieved October 24, 2009. ^ ikitommi; Daraen. "metosin/ring-http-response". Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site.
org.springframework.http. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. 10.4.5 404 Not Found The server has not found anything matching the Request-URI. Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. No URL found.
In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type. 10.4.11 410 Gone The requested resource is no longer available at the server and no forwarding address is known. HTTP Extensions for Distributed Authoring – WEBDAV. Retrieved 2016-01-09. ^ "ngx_http_special_response.c". Wikipedia As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request.
Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI. Retrieved 16 October 2015. ^ "RFC 7231, Section 6.3.4.". ^ "RFC 7230, Section 5.7.2.". ^ Simmance, Chris. "Server Response Codes And What They Mean". If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Wikipedia The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made. 208 Already Reported (WebDAV) The 208 (Already Reported) status code can be used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.