Laravel Session Middleware broken

Question

On my local system everything works fine, but after deploying Laravel 5.2 on our test system it looks like the session middleware is broken. Can someone help here?

Argument 1 passed to Illuminate\Session\Middleware\    
StartSession::addCookieToResponse() must be an instance of  
Symfony\Component\HttpFoundation\Response, boolean given, called in   
... /httpdocs/service/vendor/laravel/framework/src/Illuminate/Session 
/Middleware/StartSession.php on line 72 and defined

The global middlewares:

protected $middleware = [
    \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
    \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
    \Illuminate\Session\Middleware\StartSession::class,
    \Illuminate\View\Middleware\ShareErrorsFromSession::class,
    \App\Http\Middleware\CORSMiddleware::class,
    \LucaDegasperi\OAuth2Server\Middleware\OAuthExceptionHandlerMiddleware::class
];

score 10 · Answer 1 · edited Apr 03 '19 at 21:51

10

I had the same problem. When investigating, I discovered that at some point in my code, I used return.

It turns out (as you can see in the end of the handle method) that after executing the handle method you should always call return $next($request);.

edited Apr 03 '19 at 21:51

Cody Gray - on strike

239,200
50
490
574

answered Apr 07 '17 at 15:19

Leonardo Beal

724
11
24

Had the same problem by mistakenly commenting out ```return $next($request);``` at the end of the function – Ulterior Jan 29 '18 at 08:38
Taylor Towell says it is fixed since 5.1.1 https://github.com/laravel/lumen-framework/issues/117 but I have this error (I return error) in 5.3. Thanks for the workaround – shukshin.ivan Jun 28 '18 at 14:32

score 7 · Answer 2 · answered Aug 11 '19 at 16:35

I had similar problem in one of mine middleware (v5.8). 'Call to a member function SetCookie() on null', 'Add the CSRF token to the response cookies'

This was my code, working fine in 5.2, but failed in Laravel 5.8:

return view('pages.my_page')->with('data', $data);

changed to:

return response()->view('pages.my_page', ['data' => $data]);

Cheers!

score 4 · Answer 3 · answered Mar 17 '16 at 13:16

4

Well the addCookieToResponse method in the Illuminate\Session\Middleware\StartSession class is wanting a Response object as the first param. Make sure that you return one in all of your routes.

Here's a possible quick fix, change it to fit your case.

Before:

Route::get('hi', function() {
    return 'hi';
});

After:

Route::get('hi', function() {
    return response('hi');
});

answered Mar 17 '16 at 13:16

neochief

569
4
6

This solved my issue I was using the return statement directly in a middleware. – Mustafa Dwaikat Dec 10 '18 at 19:02

score 0 · Answer 4 · answered Apr 08 '19 at 14:00

0

In my case it was just cache. try running

php artisan config:cache

answered Apr 08 '19 at 14:00

Matteus Barbosa

2,409
20
21

score 0 · Answer 5 · answered May 12 '20 at 08:45

0

To all the people coming for this error, it's the cookie that fails.

So the fastest fix is to use another browser.
Go to settings in your browser and find the cookie and delete it.

answered May 12 '20 at 08:45

George_kane

305
3
4
17

score 0 · Answer 6 · answered Jan 07 '21 at 05:36

I had the same issue, turned out the issue for me was I changed the domain in my config/session.php in my production server


    'domain' => env('SESSION_DOMAIN', 'mydomain.com'),

on my development server which use 127.0.0.1 can't access my domain

change it to


    'domain' => env('SESSION_DOMAIN', null),

and now working fine

Laravel Session Middleware broken

6 Answers6