L5: Session store not set on request

You are not setting the MiddleWare 'Illuminate\Session\Middleware\StartSession', this could be a cause for this error.

Just a note; In 5.2 web routes should be added under web group, so that the session, csrf and other web-related middlewares get applied to them. For example, if you add auth routes outside of the web route group, you'll get the same exact error.

Let's have a quick look at Illuminate/Foundation/Http/Kernel:

protected $middlewareGroups = [
        'web' => [
            \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,
        ],

        'api' => [
            'throttle:60,1',
        ],
    ];

I am not sure if my issue is directly related to this or not. I am using Laravel 5.2 and when I call csrf_token() to get a token for a form, it returns an empty value. I dug deeper and found that a session is not being registered in SessionServiceProvider. Is there something that needs to be enabled for this to work by default? Since I am a Laravel beginner, I am not sure how to follow the advice above. How do I make sure that my routes are added under the "web" group?

Okay, so I figured out that routes need to be added within the "web" middleware group like this:

Route::group(['middleware' => 'web'], function () {
Route::get('/my-form', 'MyController@xxxx');
});

Thanks ianspangler. This same my day.

As @sepehr mensionned, all routes should be included in ['middleware' => 'web'] route group in L5.2.x

I think there is actually an issue with L5.2 as any custom error pages display this error if you try to access a session based value (e.g a login form etc).

I assume this is because the exception does not pass through the web middleware group?

To resolve and prevent the 'Session store not set on request' appearing on my custom http error pages I moved:

\Illuminate\Session\Middleware\StartSession::class,

from the web group to the global middleware group in the kernel.php file which solved the issue.

So my kernel.php file now looks like this:

namespace App\Http;

use Illuminate\Foundation\Http\Kernel as HttpKernel;

class Kernel extends HttpKernel
{
   /**
    * 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,
       \Illuminate\Session\Middleware\StartSession::class,
   ];

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

       'web' => [
           \App\Http\Middleware\EncryptCookies::class,
           \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
           \Illuminate\View\Middleware\ShareErrorsFromSession::class,
           \App\Http\Middleware\VerifyCsrfToken::class,
       ],

       'api' => [
           'throttle:60,1',
       ],
   ];

   /**
    * The application's route middleware.
    *
    * These middleware may be assigned to groups or used individually.
    *
    * @var array
    */
   protected $routeMiddleware = [
       'auth' => \App\Http\Middleware\Authenticate::class,
       'auth.basic' => \Illuminate\Auth\Middleware\AuthenticateWithBasicAuth::class,
       'guest' => \App\Http\Middleware\RedirectIfAuthenticated::class,
       'throttle' => \Illuminate\Routing\Middleware\ThrottleRequests::class,
   ];
}

If there are any better solutions I'd be glad to hear them as my grip on how to implement middleware is a little tenuous!

Thank you for posting that solution @phillipdavies. I was running into the same issue and I wasn't able to resolve it until I moved \Illuminate\Session\Middleware\StartSession::class into the global middleware. But now I'm curious if this is the "correct" solution and if it will have any potential negative performance impacts. It's really weird how I can't get a session to work with the web middleware. Can anybody shed some light on this?

there are two ways to solve this problem. The first is：move \Illuminate\Session\Middleware\StartSession::class,\Illuminate\View\Middleware\ShareErrorsFromSession::class, from the web group to the global middleware group in the kernel.php file 。 but it's just a "fix", not a solution.

The second is： keep the kernel.php file unchanged。open the routes.php, then add your own route definition into the “Application Routes” for example： before edit. Route::group(['middleware' => ['web']], function () { // });

after edit. Route::group(['middleware' => ['web']], function () { // Route::get('reg', 'login\regController@index'); Route::post('reg/register', 'login\regController@register'); });