Class UnprocessableEntityException
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.
For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.
- Exception
-
RuntimeException
-
DSchoenbauer\Exception\Platform\RuntimeException
implements
DSchoenbauer\Exception\ExceptionInterface
-
DSchoenbauer\Exception\Http\ClientError\ClientErrorException
implements
DSchoenbauer\Exception\Http\HttpExceptionInterface
-
DSchoenbauer\Exception\Http\ClientError\UnprocessableEntityException
Namespace: DSchoenbauer\Exception\Http\ClientError
Author: David Schoenbauer dschoenbauer@gmail.com
Since: 1.0.0
Link: Source
Located at Exception/Http/ClientError/UnprocessableEntityException.php
Author: David Schoenbauer dschoenbauer@gmail.com
Since: 1.0.0
Link: Source
Located at Exception/Http/ClientError/UnprocessableEntityException.php
public
|
__toString(),
__wakeup(),
getCode(),
getFile(),
getLine(),
getMessage(),
getPrevious(),
getTrace(),
getTraceAsString()
|
$code,
$file,
$line,
$message
|