Route parameters in Laravel - Step-by-Step Execution

Concept Flow - Route parameters

User visits URL

↓

Laravel checks routes

↓

Match route pattern with parameters

↓

Extract parameter values

↓

Pass parameters to controller or closure

↓

Return response with parameter data

Laravel matches the URL to a route pattern with parameters, extracts those parameters, and passes them to the handler.

Execution Sample

Laravel

Route::get('/user/{id}', function ($id) {
    return "User ID: $id";
});

Defines a route that captures the 'id' from the URL and returns it in the response.

Execution Table

Step	URL Visited	Route Pattern	Parameter Extracted	Handler Called	Response
1	/user/5	/user/{id}	id = 5	Closure with id=5	"User ID: 5"
2	/user/abc	/user/{id}	id = abc	Closure with id='abc'	"User ID: abc"
3	/user/	/user/{id}	No match	No handler	404 Not Found

💡 Execution stops when URL does not match any route pattern with required parameters.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
id	undefined	5	abc	undefined

Key Moments - 2 Insights

Why does '/user/' not match the route '/user/{id}'?

Because the route requires a parameter 'id' after '/user/', and '/user/' has nothing there, so no match occurs (see execution_table row 3).

Can the route parameter 'id' accept any value?

Yes, by default it accepts any string segment in the URL (see execution_table rows 1 and 2 where '5' and 'abc' are accepted).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'id' at step 2?

A undefined

B 5

C abc

D null

💡 Hint

Check the 'Parameter Extracted' column in execution_table row 2.

At which step does the URL fail to match the route pattern?

A Step 1

B Step 3

C Step 2

D None

💡 Hint

Look at the 'Route Pattern' and 'Parameter Extracted' columns in execution_table.

If the route was defined as '/user/{id}/profile', which URL would match?

A /user/5/profile

B /user/5

C /user/profile

D /user/5/extra

💡 Hint

The URL must exactly match the pattern including '/profile' after the parameter.

Concept Snapshot

Route parameters let Laravel capture parts of the URL as variables.
Syntax: '/path/{parameter}' captures 'parameter' from URL.
Laravel passes these to the route handler.
If URL part is missing, route does not match.
Parameters accept any string by default.

Full Transcript

When a user visits a URL, Laravel checks all defined routes to find a match. If a route has parameters like '/user/{id}', Laravel extracts the 'id' part from the URL. This value is then passed to the route's function or controller. For example, visiting '/user/5' sets 'id' to '5'. If the URL does not include the parameter, like '/user/', Laravel does not find a match and returns a 404 error. Parameters accept any string segment by default, so '/user/abc' works too. This process allows dynamic URLs that respond based on user input.