Creating middleware in Laravel - Why You Should Know This

The Big Idea

Discover how one simple layer can save you hours of repetitive coding and bugs!

The Scenario

Imagine you have to check if a user is logged in and has permission on every page manually by adding the same code in every controller method.

The Problem

Manually adding checks everywhere is repetitive, easy to forget, and makes your code messy and hard to maintain.

The Solution

Middleware lets you write this check once and apply it automatically to any route or group of routes, keeping your code clean and consistent.

Before vs After

✗ Before

if (!auth()->check()) { return redirect('login'); } // repeated in every controller method

✓ After

Route::middleware('auth')->group(function () { Route::get('/dashboard', [DashboardController::class, 'index']); });

What It Enables

You can easily control access and modify requests globally without repeating yourself.

Real Life Example

Protecting admin pages so only logged-in users with admin rights can access them, all handled by middleware.

Key Takeaways

Middleware centralizes request checks and modifications.

It prevents code duplication and errors.

It makes your app more secure and easier to maintain.

Practice

1. What is the primary purpose of middleware in Laravel?

easy

A. To define routes for the application

B. To filter and modify HTTP requests before they reach the controller

C. To create database migrations automatically

D. To generate views for the user interface

Solution

1. Step 1: Understand middleware role

   Middleware acts as a filter that processes HTTP requests before they reach the controller or after the response leaves the controller.

2. Step 2: Identify correct purpose

   Among the options, only filtering and modifying HTTP requests matches middleware's role.

3. Final Answer:

   To filter and modify HTTP requests before they reach the controller -> Option B

4. Quick Check:

   Middleware filters requests [OK]

Hint: Middleware filters requests before controllers [OK]

Common Mistakes:

• Confusing middleware with routing
• Thinking middleware creates database migrations
• Assuming middleware generates views

2. Which command correctly creates a new middleware named CheckAge in Laravel?

easy

A. php artisan make:middleware CheckAge

B. php artisan create:middleware CheckAge

C. php artisan middleware:create CheckAge

D. php artisan generate:middleware CheckAge

Solution

1. Step 1: Recall Laravel artisan command for middleware

   The correct command to create middleware is php artisan make:middleware Name.

2. Step 2: Match the command with options

   Only php artisan make:middleware CheckAge uses the exact correct syntax.

3. Final Answer:

   php artisan make:middleware CheckAge -> Option A

4. Quick Check:

   Use 'make:middleware' to create middleware [OK]

Hint: Use 'make:middleware' with artisan to create middleware [OK]

Common Mistakes:

• Using 'create:middleware' instead of 'make:middleware'
• Mixing command order or keywords
• Forgetting to specify middleware name

3. Given this middleware handle method, what will happen if the user is not authenticated?

public function handle($request, Closure $next) {
    if (!auth()->check()) {
        return redirect('login');
    }
    return $next($request);
}

medium

A. The request proceeds to the next middleware or controller

B. The request is blocked with a 403 Forbidden response

C. An error is thrown because of missing return

D. The user is redirected to the login page

Solution

1. Step 1: Analyze the authentication check

   The code checks if the user is not authenticated using !auth()->check().

2. Step 2: Understand the redirect action

   If not authenticated, it returns a redirect response to 'login', stopping further request processing.

3. Final Answer:

   The user is redirected to the login page -> Option D

4. Quick Check:

   Unauthenticated users get redirected [OK]

Hint: Redirect happens if auth check fails [OK]

Common Mistakes:

• Assuming request proceeds despite failed auth
• Thinking an error is thrown
• Confusing redirect with 403 response

4. Identify the error in this middleware handle method:

public function handle($request, Closure $next) {
    if ($request->user()->role !== 'admin') {
        abort(403, 'Unauthorized');
    }
}

medium

A. No error, this middleware is correct

B. Incorrect method name, should be handleRequest

C. Missing return statement for $next middleware call

D. Using abort() is not allowed in middleware

Solution

1. Step 1: Check middleware handle method structure

   Middleware must return either a response or call $next($request) to continue the request.

2. Step 2: Identify missing return

   This code aborts if role is not admin but does not return $next($request) if the user is admin, causing no response to be returned.

3. Final Answer:

   Missing return statement for $next middleware call -> Option C

4. Quick Check:

   Always return $next($request) to continue [OK]

Hint: Always return $next($request) in middleware [OK]

Common Mistakes:

• Forgetting to return $next($request)
• Thinking abort() is disallowed
• Renaming handle method incorrectly

5. You want to create middleware that blocks requests with a query parameter blocked=true by aborting with a 403 Forbidden response. Which handle method implementation correctly achieves this?

hard

A. public function handle($request, Closure $next) {
if ($request->query('blocked') === 'true') {
abort(403, 'Access denied');
}
return $next($request);
}

B. public function handle($request, Closure $next) {
if ($request->input('blocked') == true) {
return redirect('home');
}
return $next($request);
}

C. public function handle($request, Closure $next) {
if ($request->blocked === true) {
abort(404);
}
return $next($request);
}

D. public function handle($request, Closure $next) {
if ($request->has('blocked')) {
return response('Blocked', 401);
}
return $next($request);
}

Solution

1. Step 1: Check how to read query parameters

   Use $request->query('blocked') to get the query parameter value as string.

2. Step 2: Verify condition and response

   public function handle($request, Closure $next) { if ($request->query('blocked') === 'true') { abort(403, 'Access denied'); } return $next($request); } checks if 'blocked' equals string 'true' and aborts with 403, then returns next middleware call.

3. Step 3: Compare other options

   public function handle($request, Closure $next) { if ($request->input('blocked') == true) { return redirect('home'); } return $next($request); } uses input() and redirects instead of aborting; public function handle($request, Closure $next) { if ($request->blocked === true) { abort(404); } return $next($request); } accesses property incorrectly; public function handle($request, Closure $next) { if ($request->has('blocked')) { return response('Blocked', 401); } return $next($request); } returns 401 but blocks any 'blocked' param regardless of value.

4. Final Answer:

   Checks $request->query('blocked') === 'true' and uses abort(403, 'Access denied') -> Option A

5. Quick Check:

   Use $request->query('blocked') and abort(403) [OK]

Hint: Use $request->query('param') and abort(403) to block [OK]

Common Mistakes:

• Using $request->blocked instead of query()
• Returning redirect instead of abort
• Not checking exact 'true' string value