Http Error Code 2xx
This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. 10.5.3 502 Bad Gateway The server, while Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, Oracle. have a peek at these guys
These status codes are applicable to any request method. User agents should display any included entity to the user. 400 Bad Request The request could not be understood by the server due to malformed syntax. Wikipedia A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via This response is cacheable unless indicated otherwise.
Http Status Code 400
Like the found response, this suggests that the client go try another network address. Transparent Content Negotiation in HTTP. This response MUST NOT use the multipart/byteranges content- type. 10.4.18 417 Expectation Failed The expectation given in an Expect request-header field (see section 14.20) could not be met by this server,
Other services may wish to implement the 429 Too Many Requests response code instead. 422 Unprocessable Entity (WebDAV) The 422 (Unprocessable Entity) status code means the server understands the content type Retrieved 16 October 2015. ^ "Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect". https://tools.ietf.org/html/rfc2774. Http Code 302 Used for conditional GET calls to reduce band-width usage.
Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. Http Response Example User agents SHOULD display any included entity to the user. Wikipedia Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons. 306 (Unused) The 306 status code was used https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the
the user does not have the necessary credentials. Http Code 403 Retrieved 7 March 2015. ^ "Server Error Codes". RFC 2616. Wikipedia The request is larger than the server is willing or able to process. 414 Request-URI Too Long The server is refusing to service the request because the Request-URI is longer
Http Response Example
OK 200 The request was fulfilled. http://www.restapitutorial.com/httpstatuscodes.html The client MAY repeat the request without modifications at any later time." 409 Conflict The request could not be completed due to a conflict with the current state of the resource. Http Status Code 400 The server MUST send a final response after the request has been completed. Http Status Codes Cheat Sheet Previously called "Request Entity Too Large". 414 URI Too Long (RFC 7231) The URI provided was too long for the server to process.
Wikipedia Indicates that the resource requested is no longer available and will not be available again. More about the author The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34). httpstatus. a PROPPATCH). 425 Reserved for WebDAV Slein, J., Whitehead, E.J., et al., "WebDAV Advanced Collections Protocol", Work In Progress. Http 422
Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, some Web applications and frameworks use the 302 status code as if it were the 303. For example, a POST request should be repeated using another POST request. 308 Permanent Redirect (RFC 7538) The request and all future requests should be repeated using another URI. 307 and 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. check my blog Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request.
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 Http 404 Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being Retrieved 16 October 2015. ^ Holtman, Koen; Mutz, Andrew H. (March 1998).
More REST service-specific information is contained in the entry.
The actual current instance might not be available except by combining this response with other previous or future responses, as appropriate for the specific instance-manipulation(s). 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 Got it! Http 502 For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server.
March 2015. The entity format is specified by the media type given in the Content-Type header field. Retrieved June 30, 2012. ^ "303". news A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message.
DELETE). 205 Reset Content The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. The entity format is specified by the media type given in the Content-Type header field. Error code response for missing or invalid authentication token. 402 Payment Required This code is reserved for future use. For example, this code could be used to present multiple video format options, to list files with different extensions, or to suggest word sense disambiguation. 301 Moved Permanently This and all
As from the point of view of the clientand the HTTP transaction the other service is hidden within the server, this maybe treated identically to Internal error 500, but has more Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK). 10.2.5 204 No Content The server has fulfilled the request but If the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response.
Not Modified 304 If the client has done a conditional GET and access is allowed, but the document has not been modified since the date and time specified in If-Modified-Since field, The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. 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 Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
Msdn.microsoft.com. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. Date 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 Originally meant "Subsequent requests should use the specified proxy." 307 Temporary Redirect (since HTTP/1.1) In this case, the request should be repeated with another URI; however, future requests should still use