Route middleware in Laravel - Step-by-Step Execution

Concept Flow - Route middleware

Request comes in

↓

Route matched

↓

Middleware stack starts

↓

Middleware 1: Check condition

Yes No↓

Pass

↓

Middleware 2: Next check

↓

Controller or final handler

↓

Response sent back

When a request matches a route, Laravel runs middleware in order. Each middleware can allow the request to continue or stop it with a response.

Execution Sample

Laravel

Route::middleware(['auth', 'verified'])->get('/dashboard', function () {
    return 'Welcome!';
});

This route uses 'auth' and 'verified' middleware before showing the dashboard.

Execution Table

Step	Middleware	Condition Checked	Result	Action Taken	Next Step
1	auth	Is user logged in?	Yes	Pass request to next middleware	Go to Step 2
2	verified	Is user email verified?	Yes	Pass request to controller	Go to Step 3
3	controller	N/A	N/A	Return 'Welcome!'	Send response
Exit	N/A	N/A	N/A	Response sent back to client	End

💡 Middleware passed all checks; controller returned response; response sent to client.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
request_status	Incoming request	Authenticated	Verified	Handled by controller
response	None	None	None	'Welcome!' string

Key Moments - 3 Insights

What happens if the 'auth' middleware fails?

If 'auth' fails (user not logged in), it stops the request and returns a redirect or error immediately, so later middleware and controller do not run. See Step 1 in execution_table.

Can middleware modify the request before passing it on?

Yes, middleware can change the request or add data before passing it to the next middleware or controller. This happens between steps in the middleware stack.

Why is middleware order important?

Middleware run in the order listed. If an early middleware blocks the request, later ones never run. So order controls which checks happen first.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of the 'auth' middleware at Step 1?

A User is authenticated, request passes on

B User is not authenticated, request blocked

C User email is verified

D Controller returns response

💡 Hint

Check the 'Result' column for Step 1 in execution_table

At which step does the controller handle the request?

A Step 1

B Step 2

C Step 3

D Exit

💡 Hint

Look for 'controller' in the Middleware column in execution_table

If the 'verified' middleware fails, what happens next?

A Request continues to controller

B Request is blocked and response sent immediately

C Next middleware runs

D Request is retried

💡 Hint

See the branching logic in concept_flow and Step 2 in execution_table

Concept Snapshot

Route middleware runs before the controller.
Each middleware checks conditions.
If a middleware fails, it stops the request.
Middleware run in the order listed.
If all pass, controller handles the request.
Response then returns to client.

Full Transcript

When a web request comes to Laravel, it first finds the matching route. Before running the route's controller, Laravel runs middleware in the order they are listed. Each middleware checks something, like if the user is logged in or email verified. If a middleware check fails, it stops the request and sends a response, like a redirect or error. If it passes, the request moves to the next middleware. After all middleware pass, the controller runs and returns a response. This response then goes back to the user. Middleware order matters because the first failure stops everything else.