Laravel middleware won't run before every request

Question

I have this simple middleware

<?php

namespace App\Http\Middleware;

use Closure;
use Session;
use App;

class SetPageLanguage
{
    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure  $next
     * @return mixed
     */
    public function handle($request, Closure $next)
    {

        if(Session::has('language'))
        {
            $lang = Session::get('language');

            App::setLocale($lang); // still don't know which one to use, but I'll figure it out ;)
            app()->setLocale($lang);
        }

        return $next($request);
    }
}

Which is supposed to run before every single request. So I added it to the kernel:

class Kernel extends HttpKernel
{

    protected $middleware = [

        ...

        \App\Http\Middleware\SetPageLanguage::class, // middleware for setting the language when loading a page
    ];

But it doesn't work. It never runs.

On the other hand, if I put it in routeMiddleware, like so:

 protected $routeMiddleware = [

        ...

        'localization' => \App\Http\Middleware\SetPageLanguage::class,

        ...

And call it on every route, like, for example:

Route::GET('/', 'AnonymController@home')->middleware('localization');

It works perfectly! But I don't want to have to do that. I want it to run automatically before every single request, like it is supposed to. What am I missing?

I'm quite new to laravel and Php, so I'm sure I'm not understandig something important.

I watched some tutorials, read a few articles and searched for the answer here on Stack Overflow. Still can't figure it out.

How can I make my middleware run before every single request?

Thank you.

Devon Bessemer · Accepted Answer · 2018-11-03 14:15:04Z

3

It likely is running, but global middleware run before route middleware. It's important to understand what the other middleware are doing and the order they are called.

If you look at the 'web' middleware group, you'll see this middleware:

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

Sessions are not instantly available in a Laravel app. The StartSession middleware is what starts sessions for web routes. API routes don't use sessions because they are stateless.

Therefore, this middleware likely belongs in the web group below the session middlewares since it relies on session data.

answered Nov 3, 2018 at 14:15

Devon Bessemer

35.6k10 gold badges77 silver badges102 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Luís Henriques Over a year ago

So you mean they run in the order they are presented? First middleware, then middlewareGroups, then routeMiddleware? Good to know. I added it at the bottom of the web group, in middlewareGroups, after StartSession. It works perfectly now. Thank you.

Devon Bessemer Over a year ago

Yes, that is how they run, but the middleware groups and route middleware aren't global, they are dependent on the route definitions. Any route in routes/web.php will be using the web group. Then route middleware are route specific. So middleware are defined at a global level, group level, and route level.

Collectives™ on Stack Overflow

Laravel middleware won't run before every request

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related