Session variables inside ExceptionHandler are not working

If you not planning to use stateless api's move the contents of web middleware group to global middleware stack. Session will always be created then.

Thank you premsaurav for your answer.

Let me see if I understood your answer, because I'm working with Laravel 5.2 only for 4 days and I'm not very familiar with the terminology. :(

Moving my middleware from web to $routeMiddleware, I get the same error Moving the middleware at protected $middleware I have a "Session store not set on request" error The same combination of errors I get when I move Route inside or outside the web group, or when I assign I new group to them. I have tried, also to use "Session::" instead of "$request->session" but again the error I receive it depends on the combination. On every case when an error is fired up, the middleware is not called or if It called has no session or request!

Is this what your mean, or I understood it wrongly?

Thanks you, for your time.

PS: Please keep in mind I work on 5.2 and if I understood correctly, on 5.2 they changed, how sessions are managed internally.

What i meant, is that in your kernel, it should look something like, and don't use web group. You will then have access to session for each request, unless something else is screwed up.

 /**
     * The application's global HTTP middleware stack.
     *
     * These middleware are run during every request to your application.
     *
     * @var array
     */
    protected $middleware = [
           \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
           \App\Http\Middleware\EncryptCookies::class,
            \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
            \Illuminate\Session\Middleware\StartSession::class,
            \Illuminate\View\Middleware\ShareErrorsFromSession::class,
            \App\Http\Middleware\VerifyCsrfToken::class,
    ];

    /**
     * The application's route middleware groups.
     *
     * @var array
     */
    protected $middlewareGroups = [
    ];

Thank you again premsaurav.

Unfortunately... if I move the middleware at the global stack, I get the "Session store not set on request". According Matt's blog post:

anything that's not given a web middleware will not have cookies or session or CSRF functional.

...and I cannot find in the documentation or in the web, if and how it's possible to initialize the session on my own middleware :(

Unfortunately... if I move the middleware at the global stack, I get the "Session store not set on request".

Show the full error trace ?.

anything that's not given a web middleware will not have cookies or session or CSRF functional.

This is conditionally true, will explain later.

RuntimeException in Request.php line 794:
Session store not set on request.

in Request.php line 794
at Request->session() in CheckSessionMiddleware.php line 22
at CheckSessionMiddleware->handle(object(Request), object(Closure))
at call_user_func_array(array(object(CheckSessionMiddleware), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 124
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in CheckForMaintenanceMode.php line 44
at CheckForMaintenanceMode->handle(object(Request), object(Closure))
at call_user_func_array(array(object(CheckForMaintenanceMode), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 124
at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing\{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 103
at Pipeline->then(object(Closure)) in Kernel.php line 132
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 99
at Kernel->handle(object(Request)) in index.php line 54

The line 22 contains the attempt to access the $request->session()

What is this? CheckSessionMiddleware(), if at all using this move it below StartSession middleware.

Hmm... You just gave me the idea!!!

CheckSessionMiddleware() is my middleware which performs the required session checks. The output of the previous message, is the error trace when the middleware is located at global stack, using Laravel's "default" way

protected $middleware = [
        \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
        \App\Http\Middleware\CheckSessionMiddleware::class,
];

Reading your comment I decided to include \Illuminate\Session\Middleware\StartSession::class (used at web group) also at the global stack, before my middleware like this:

protected $middleware = [
        \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
        \Illuminate\Session\Middleware\StartSession::class,
        \App\Http\Middleware\CheckSessionMiddleware::class,
];

Now the application works fine. The sessions are there to use them and the view (which uses sesssion variables) that created at the ExceptionHandler works fine. I'm not sure it's the right way but at least it works.

I believe it will be better to keep using the web group and include there the Exception class, after my middleware but I didn't find out yet what to include.

Thank you for your help ...and any other idea, is welcomed