Error Handling

    When you start a new Laravel project, error and exception handling is already configured for you. The class is where all exceptions triggered by your application are logged and then rendered back to the user. We'll dive deeper into this class throughout this documentation.

    The debug option in your config/app.php configuration file determines how much information about an error is actually displayed to the user. By default, this option is set to respect the value of the APP_DEBUG environment variable, which is stored in your .env file.

    For local development, you should set the APP_DEBUG environment variable to true. In your production environment, this value should always be false. If the value is set to true in production, you risk exposing sensitive configuration values to your application's end users.

    All exceptions are handled by the App\Exceptions\Handler class. This class contains two methods: report and render. We'll examine each of these methods in detail. The report method is used to log exceptions or send them to an external service like , Bugsnag or . By default, the report method passes the exception to the base class where the exception is logged. However, you are free to log exceptions however you wish.

    Global Log Context

    If available, Laravel automatically adds the current user's ID to every exception's log message as contextual data. You may define your own global contextual data by overriding the context method of your application's App\Exceptions\Handler class. This information will be included in every exception's log message written by your application:

    1. /**
    2.  * Get the default context variables for logging.
    3.  *
    4.  * @return array
    5.  */
    6. protected function context()
    7. {
    8.     return array_merge(parent::context(), [
    9.         'foo' => 'bar',
    10. }

    The report Helper

    Sometimes you may need to report an exception but continue handling the current request. The report helper function allows you to quickly report an exception using your exception handler's report method without rendering an error page:

    1. public function isValid($value)
    2. {
    4.         // Validate the value...
    5.     } catch (Exception $e) {
    6.         report($e);
    8.         return false;
    9.     }
    10. }

    Ignoring Exceptions By Type

    The $dontReport property of the exception handler contains an array of exception types that will not be logged. For example, exceptions resulting from 404 errors, as well as several other types of errors, are not written to your log files. You may add other exception types to this array as needed:

    The render method is responsible for converting a given exception into an HTTP response that should be sent back to the browser. By default, the exception is passed to the base class which generates a response for you. However, you are free to check the exception type or return your own custom response:

    1. /**
    2.  * Render an exception into an HTTP response.
    3.  *
    4.  * @param  \Illuminate\Http\Request  $request
    5.  * @param  \Exception  $exception
    6.  * @return \Illuminate\Http\Response
    7.  */
    8. public function render($request, Exception $exception)
    9. {
    10.     if ($exception instanceof CustomException) {
    11.         return response()->view('errors.custom', [], 500);
    12.     }
    14.     return parent::render($request, $exception);
    15. }

    1. <?php
    4. use Exception;
    6. class RenderException extends Exception
    7. {
    8.     /**
    9.      * Report the exception.
    10.      *
    11.      * @return void
    12.      */
    13.     public function report()
    14.     {
    15.         //
    16.     }
    18.     /**
    19.      * Render the exception into an HTTP response.
    20.      *
    21.      * @param  \Illuminate\Http\Request  $request
    22.      * @return \Illuminate\Http\Response
    23.      */
    24.     public function render($request)
    25.     {
    26.         return response(...);
    27.     }
    28. }

    {tip} You may type-hint any required dependencies of the report method and they will automatically be injected into the method by Laravel's .

    Some exceptions describe HTTP error codes from the server. For example, this may be a "page not found" error (404), an "unauthorized error" (401) or even a developer generated 500 error. In order to generate such a response from anywhere in your application, you may use the abort helper:

    The abort helper will immediately raise an exception which will be rendered by the exception handler. Optionally, you may provide the response text:

    1. abort(403, 'Unauthorized action.');

    Laravel makes it easy to display custom error pages for various HTTP status codes. For example, if you wish to customize the error page for 404 HTTP status codes, create a resources/views/errors/404.blade.php. This file will be served on all 404 errors generated by your application. The views within this directory should be named to match the HTTP status code they correspond to. The HttpException instance raised by the abort function will be passed to the view as an $exception variable:

    1. <h2>{{ $exception->getMessage() }}</h2>

    You may publish Laravel's error page templates using the vendor:publish Artisan command. Once the templates have been published, you may customize them to your liking: