Controller middleware in Laravel - Step-by-Step Execution

Concept Flow - Controller middleware

Request comes in

↓

Controller Middleware

↓

Pass

↓

Controller Action

↓

Send Response

The request first hits the controller middleware which can either allow it to continue to the controller action or block it and return a response immediately.

Execution Sample

Laravel

public function __construct()
{
    $this->middleware('auth');
}

public function index()
{
    return view('dashboard');
}

This code applies the 'auth' middleware to the controller, so only authenticated users can access the index method.

Execution Table

Step	Action	Middleware Check	Result	Next Step
1	Request arrives at controller	Check 'auth' middleware	User authenticated?	Yes -> Proceed, No -> Block
2	User authenticated?	Yes	Pass middleware	Call index() method
3	Call index() method	No middleware check	Return dashboard view	Send response
4	Send response	No middleware check	Response sent to user	End
5	If user not authenticated	No	Block request	Redirect to login

💡 Execution stops when response is sent or request is blocked by middleware.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Request	Incoming HTTP request	Checked by middleware	Passed to controller	Handled by index()	Response sent
User Authenticated	Unknown	Checked	True or False	N/A	N/A

Key Moments - 2 Insights

Why does the middleware block the request before the controller method runs?

Because middleware acts as a gatekeeper. If the user is not authenticated (see execution_table step 5), the middleware stops the request and redirects before the controller method executes.

Can middleware modify the request or response?

Yes, middleware can change the request before passing it on or modify the response before sending it back, but in this example it only checks authentication (execution_table steps 1-2).

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 2 if the user is authenticated?

A The middleware passes the request to the controller

B The middleware blocks the request

C The request is redirected to login

D The response is sent immediately

💡 Hint

Check the 'Result' and 'Next Step' columns in execution_table row 2

At which step does the controller method 'index' get called?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' column in execution_table row 3

If the user is not authenticated, what does the middleware do according to the execution table?

A Passes the request to the controller

B Returns the dashboard view

C Blocks the request and redirects to login

D Sends the response immediately

💡 Hint

See execution_table row 5 under 'Result' and 'Next Step'

Concept Snapshot

Controller middleware in Laravel acts as a filter for requests.
It runs before controller methods.
Middleware can allow or block requests.
Example: 'auth' middleware blocks unauthenticated users.
Middleware can redirect or modify requests/responses.
Applied in controller constructor with $this->middleware('name').

Full Transcript

In Laravel, controller middleware runs before the controller's methods. When a request arrives, the middleware checks conditions like user authentication. If the user passes the check, the request proceeds to the controller method, which then returns a response. If the user fails, the middleware blocks the request and can redirect the user, for example, to a login page. This process ensures only authorized users access certain controller actions. Middleware is applied in the controller's constructor using $this->middleware('auth'). This flow helps keep your application secure and organized.