Things go wrong. You can’t predict errors, but you can anticipate them. Each Slim Framework application has an error handler that receives all uncaught PHP exceptions. This error handler also receives the current HTTP request and response objects, too. The error handler must prepare and return an appropriate Response object to be returned to the HTTP client.
The default error handler is very basic. It sets the Response status code to
500, it sets the Response content type to
text/html, and appends a generic error message into the Response body.
This is probably not appropriate for production applications. You are strongly encouraged to implement your own Slim application error handler.
The default error handler can also include detailed error diagnostic information. To enable this you need to set the
displayErrorDetails setting to true:
A Slim Framework application’s error handler is a Pimple service. You can substitute your own error handler by defining a custom Pimple factory method with the application container.
There are two ways to inject handlers:
In this example, we define a new
errorHandler factory that returns a callable. The returned callable accepts three arguments:
The callable MUST return a new
\Psr\Http\Message\ResponseInterface instance as is appropriate for the given exception.
Error handlers may also be defined as an invokable class.
and attached like so:
This allows us to define more sophisticated handlers or extend/override the
Please note: The following four types of exceptions will not be handled by a custom
Slim\Exception\MethodNotAllowedException: This can be handled via a custom
Slim\Exception\NotFoundException: This can be handled via a custom
Slim\Exception\SlimException: This type of exception is internal to Slim, and its handling cannot be overridden.
To completely disable Slim’s error handling, simply remove the error handler from the container:
You are now responsible for handling any exceptions that occur in your application as they will not be handled by Slim.