Namespace DSchoenbauer\Exception\Http\ClientError

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

The request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request.

The method received in the request-line is known by the origin server but not supported by the target resource.

The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

The server is refusing to process a request because the request payload is larger than the server is willing or able to process.

The request has not been applied because it lacks valid authentication credentials for the target resource.

Intended to be used when resource access is denied for legal reasons, e.g. censorship or government-mandated blocked access. A reference to the 1953 dystopian novel Fahrenheit 451, where books are outlawed, and the autoignition temperature of paper, 451°F.

The server understands the content type of the request entity (hence a 415 Unsupported Media Type status code is inappropriate), and the syntax of the request entity is correct (thus a 400 Bad Request status code is inappropriate) but was unable to process the contained instructions.

The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.

The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.