Module "httpStatus"

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. For example the JSON body could not be parsed.

The request was understood, and semantically correct, but conflicts with the current state. For example: the type is locked.

The expectation given in the request's Expect header field could not be met.

The user is authenticated but does not have permission.

Access to the target resource is no longer available at the origin server and this condition is likely to be permanent.

The server refuses to accept the request without a defined Content-Length.

The resource does not support the given method. The origin server MUST generate an Allow header field containing a list of the supported methods.

The target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request.

The requested resource was not found.

The request is larger than the server is willing or able to process.

The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.

The user has sent too many requests in a given amount of time.

Authentication is required and the user is not logged in.

The request is syntactically correct, but contains semantic errors. For example a string was expected but got a number.

The request type has a media type which the server or resource does not support.

The resource moved temporarily. Browsers will change POST to GET on redirect. Search engines will not update their index.

The resource moved permanently. Browsers will change POST to GET on redirect. Search engines will update their index.

The target resource has more than one representation, each with its own more specific identifier, and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to one or more of those identifiers.

Cache hit. No content is sent. This is determined by the request headers If-Modified-Since or If-None-Match.

The resource moved permanently and browsers should resubmit, preserving the method and body. Don't use for GET. Search engines will not update their index.

The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request.

The resource moved temporarily and browsers should resubmit, preserving the method and body. Don't use for GET. Search engines will update their index.

Received an invalid response from an inbound server it accessed while acting as a proxy.

Did not receive a timely response from an upstream server while acting as a proxy.

Generic server-side error.

Usually implies future availability.

A service is temporarily down.

The request has been accepted for processing, but the processing has not been completed. The primary resource created by the request is identified by either a Location header field in the response or, if no Location field is received, by the effective request URI.

The request has been fulfilled and has resulted in one or more new resources being created.

The request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy.

The server has successfully fulfilled the request and there is no content to send in the response payload body.

The request has succeeded. The payload depends on the request method.

The server has fulfilled the request and desires that the user agent reset the "document view", which caused the request to be sent, to its original state as received from the origin server.