Middleware groups in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a route uses a middleware group?

In Laravel, if a route is assigned a middleware group, what is the effect on the request?

A All middleware in the group run in the order they are listed before the controller handles the request.

B Only the first middleware in the group runs, skipping the rest.

C Middleware in the group run randomly depending on server load.

D Middleware groups are ignored unless explicitly called inside the controller.

💡 Hint

Think about how middleware acts as a chain of filters on the request.

Middleware groups run all their middleware in the order defined. This ensures each middleware can process or modify the request before it reaches the controller.

📝 Syntax

intermediate

Which code correctly defines a middleware group in Laravel?

Choose the correct way to define a middleware group named 'web' that includes 'auth' and 'verified' middleware.

A 'web' => ['auth|verified'],

B 'web' => 'auth, verified',

C 'web' => ['auth', 'verified'],

D 'web' => ['auth' & 'verified'],

💡 Hint

Middleware groups are arrays of middleware names.

Middleware groups are defined as arrays listing each middleware by its key name. Commas separate the middleware.

❓ state_output

advanced

What is the output when a middleware in a group aborts the request?

Given a middleware group with two middleware: 'checkAge' and 'logAccess'. If 'checkAge' aborts the request with a 403 error, what happens?

A 'logAccess' runs first, then 'checkAge' aborts with 403.

B The request stops immediately with a 403 response; 'logAccess' does not run.

C Both middleware run, but the response is 403 after completion.

D The request continues normally ignoring the abort.

💡 Hint

Consider how middleware can stop the request chain.

If a middleware aborts the request, Laravel stops running further middleware and returns the error response immediately.

🔧 Debug

advanced

Why does this middleware group not apply to routes?

Given this middleware group definition in Kernel.php:

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

And routes using middleware('api'), but authentication fails unexpectedly. What is the likely cause?

A Middleware groups cannot be used with API routes.

B The 'throttle:60,1' middleware disables authentication.

C The middleware group name 'api' is reserved and cannot be customized.

D The 'auth:api' middleware requires a guard that is not configured properly.

💡 Hint

Check the guard configuration for 'auth:api'.

The 'auth:api' middleware uses a guard that must be set up in auth.php. If missing or misconfigured, authentication fails.

🧠 Conceptual

expert

How does Laravel prioritize middleware in groups vs route middleware?

Consider a route that uses both a middleware group and an individual middleware assigned directly. Which middleware runs first?

A The individual middleware runs first, then the group middleware run in order.

B Middleware in the group run first in order, then the individual middleware runs after.

C Middleware order is random between group and individual middleware.

D Only the individual middleware runs, group middleware are ignored.

💡 Hint

Think about how Laravel stacks middleware for a route.

Laravel runs middleware assigned directly on the route before middleware in groups. This allows specific middleware to run earlier.

Practice

1. What is the main purpose of middleware groups in Laravel?

easy

A. To bundle multiple middleware under one name for easy use

B. To create database migrations automatically

C. To define routes in a separate file

D. To handle user authentication only

Solution

1. Step 1: Understand middleware groups concept

   Middleware groups combine several middleware into one named group.

2. Step 2: Identify the purpose of grouping

   This grouping allows applying multiple middleware easily by referencing the group name in routes.

3. Final Answer:

   To bundle multiple middleware under one name for easy use -> Option A

4. Quick Check:

   Middleware groups = bundle middleware [OK]

Hint: Middleware groups bundle middleware for simpler route use [OK]

Common Mistakes:

• Confusing middleware groups with route definitions
• Thinking middleware groups create migrations
• Assuming middleware groups only handle authentication

2. Which file in a Laravel project defines middleware groups?

easy

A. routes/web.php

B. app/Http/Kernel.php

C. config/app.php

D. app/Providers/RouteServiceProvider.php

Solution

1. Step 1: Recall where middleware is registered

   Middleware and middleware groups are registered in the Kernel class.

2. Step 2: Identify the Kernel file location

   In Laravel, this is app/Http/Kernel.php.

3. Final Answer:

   app/Http/Kernel.php -> Option B

4. Quick Check:

   Middleware groups in Kernel.php [OK]

Hint: Middleware groups live in Kernel.php file [OK]

Common Mistakes:

• Choosing route files instead of Kernel.php
• Confusing config files with middleware registration
• Selecting service providers incorrectly

3. Given this Kernel.php snippet:

protected $middlewareGroups = [
    'web' => [
        \App\Http\Middleware\EncryptCookies::class,
        \App\Http\Middleware\VerifyCsrfToken::class,
    ],
];

What happens when you apply the 'web' middleware group to a route?

medium

A. Both EncryptCookies and VerifyCsrfToken middleware run

B. Only VerifyCsrfToken middleware runs

C. No middleware runs because groups are ignored

D. Only EncryptCookies middleware runs

Solution

1. Step 1: Examine the 'web' middleware group contents

   The 'web' group contains two middleware classes: EncryptCookies and VerifyCsrfToken.

2. Step 2: Understand group application effect

   Applying the 'web' group runs all middleware listed inside it.

3. Final Answer:

   Both EncryptCookies and VerifyCsrfToken middleware run -> Option A

4. Quick Check:

   Middleware group runs all its middleware [OK]

Hint: Middleware group runs all middleware inside it [OK]

Common Mistakes:

• Thinking only one middleware runs per group
• Assuming groups are ignored in routes
• Confusing middleware with route middleware

4. You added a new middleware to a group in Kernel.php but it does not run on routes using that group. What is a likely cause?

medium

A. You forgot to register the middleware class in the group array

B. Middleware groups cannot be modified after Laravel installation

C. Middleware groups only work with API routes

D. You did not clear the route cache after changes

Solution

1. Step 1: Understand middleware group modification

   Adding middleware to a group requires updating the Kernel.php file correctly.

2. Step 2: Recognize caching impact

   Laravel caches routes and middleware; changes require clearing cache to take effect.

3. Final Answer:

   You did not clear the route cache after changes -> Option D

4. Quick Check:

   Clear cache after middleware changes [OK]

Hint: Clear route cache after changing middleware groups [OK]

Common Mistakes:

• Assuming middleware groups are immutable
• Forgetting to clear cache after edits
• Thinking middleware groups only apply to API routes

5. You want to create a new middleware group called admin that includes the auth middleware and a custom CheckAdmin middleware. How should you define it in Kernel.php?

hard

A. 'admin' => [\App\Http\Middleware\Auth::class, 'CheckAdmin'],

B. 'admin' => ['auth', 'CheckAdmin'],

C. 'admin' => ['auth', \App\Http\Middleware\CheckAdmin::class],

D. 'admin' => [\App\Http\Middleware\auth::class, \App\Http\Middleware\CheckAdmin::class],

Solution

1. Step 1: Identify correct middleware references

   Middleware classes must be referenced by their full class name with namespace or by middleware alias strings registered in Kernel.

2. Step 2: Use middleware alias for 'auth' and class for custom middleware

   'auth' is usually an alias, so it can be a string. Custom middleware must be referenced by full class name.

3. Final Answer:

   'admin' => ['auth', \App\Http\Middleware\CheckAdmin::class], -> Option C

4. Quick Check:

   Use alias for built-in, class for custom middleware [OK]

Hint: Use alias strings for built-in, full class for custom middleware [OK]

Common Mistakes:

• Using lowercase class names incorrectly
• Using strings for custom middleware without alias
• Mixing alias and class references wrongly