Route prefixes in Laravel - Step-by-Step Execution

Concept Flow - Route prefixes

Define Route Group with Prefix

↓

Add Routes inside Group

↓

Request URL matches prefix?

No→No Match

Yes↓

Match Route inside Group

↓

Execute Route Action

This flow shows how Laravel groups routes with a prefix, then matches incoming URLs starting with that prefix to the correct route inside the group.

Execution Sample

Laravel

Route::prefix('admin')->group(function () {
    Route::get('dashboard', function () {
        return 'Admin Dashboard';
    });
});

Defines a route group with prefix 'admin' and a route 'dashboard' inside it that returns a string.

Execution Table

Step	Action	Request URL	Prefix Check	Route Matched	Response
1	Request to '/admin/dashboard'	/admin/dashboard	Matches 'admin' prefix	Matches 'dashboard' route	'Admin Dashboard' returned
2	Request to '/dashboard'	/dashboard	Does NOT match 'admin' prefix	No route matched	404 Not Found
3	Request to '/admin/profile'	/admin/profile	Matches 'admin' prefix	No matching route inside group	404 Not Found

💡 Execution stops when a matching route is found or no routes match the request URL.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
Request URL	''	/admin/dashboard	/dashboard	/admin/profile
Prefix Matched	false	true	false	true
Route Matched	false	true	false	false
Response	''	'Admin Dashboard'	'404 Not Found'	'404 Not Found'

Key Moments - 2 Insights

Why does '/dashboard' not match the prefixed route?

Because the prefix 'admin' must be at the start of the URL. '/dashboard' lacks the 'admin' prefix, so it does not match the group routes (see execution_table row 2).

What happens if the URL matches the prefix but no route inside the group matches?

Laravel returns a 404 Not Found because it finds the prefix but no specific route inside the group matches the rest of the URL (see execution_table row 3).

Visual Quiz - 3 Questions

Look at the execution table, what is the response when the request URL is '/admin/dashboard'?

A 'Admin Dashboard'

B '404 Not Found'

C Empty response

D 'dashboard'

💡 Hint

Check the Response column in execution_table row 1.

At which step does the prefix check fail?

A Step 1

B Step 2

C Step 3

D None

💡 Hint

Look at the Prefix Check column in execution_table row 2.

If we add a route 'profile' inside the prefix group, what would be the response for '/admin/profile'?

A '404 Not Found'

B Empty response

C 'Admin Profile'

D 'Admin Dashboard'

💡 Hint

Consider execution_table row 3 and what changes if a matching route exists.

Concept Snapshot

Laravel Route Prefixes:
- Use Route::prefix('prefix')->group() to add a URL prefix to routes.
- All routes inside the group start with the prefix.
- Incoming URLs must start with the prefix to match these routes.
- If prefix matches but no route inside matches, 404 is returned.
- Helps organize routes under common URL parts.

Full Transcript

This visual execution trace shows how Laravel handles route prefixes. First, a route group is defined with a prefix like 'admin'. Routes inside this group automatically have URLs starting with 'admin/'. When a request comes in, Laravel checks if the URL starts with the prefix. If it does, it tries to match the rest of the URL to a route inside the group. If a match is found, the route's action runs and returns a response. If no match is found inside the group, Laravel returns a 404 error. If the URL does not start with the prefix, Laravel skips this group and tries other routes. This helps organize routes that share a common URL part, like admin pages.

Practice

1. What is the main purpose of using Route::prefix() in Laravel?

easy

A. To register routes in a different file

B. To change the HTTP method of routes

C. To define middleware for routes

D. To add a common URL segment to a group of routes

Solution

1. Step 1: Understand what Route::prefix() does

   This method adds a common URL segment to all routes inside the group, making URLs organized.

2. Step 2: Compare with other options

   Changing HTTP methods, middleware, or file registration are done differently, not by prefix.

3. Final Answer:

   To add a common URL segment to a group of routes -> Option D

4. Quick Check:

   Route prefix = common URL part [OK]

Hint: Prefix means adding a shared start to URLs [OK]

Common Mistakes:

• Confusing prefix with middleware
• Thinking prefix changes HTTP methods
• Assuming prefix changes route files

2. Which of the following is the correct syntax to define a route group with the prefix admin using Route::prefix() in Laravel?

easy

A. Route::group(['prefix' => 'admin'], function () { /* routes */ });

B. Route::prefix('admin')->group(function () { /* routes */ });

C. Route::prefix('admin', function () { /* routes */ });

D. Route::group('admin', function () { /* routes */ });

Solution

1. Step 1: Recall Laravel prefix group syntax

   The correct syntax uses Route::prefix('admin')->group(function () { ... });.

2. Step 2: Identify incorrect options

   Route::group(['prefix' => 'admin'], function () { /* routes */ }); uses group() with array instead of prefix(). Route::prefix('admin', function () { /* routes */ }); incorrectly passes closure as second argument to prefix(). Route::group('admin', function () { /* routes */ }); passes string directly to group().

3. Final Answer:

   Route::prefix('admin')->group(function () { /* routes */ }); -> Option B

4. Quick Check:

   Use prefix()->group() for route prefixes [OK]

Hint: Use prefix('name')->group() for clean route groups [OK]

Common Mistakes:

• Passing prefix as second argument to prefix()
• Using group() without prefix()
• Using array syntax incorrectly

3. Given the following Laravel routes code, what URL will respond to the DashboardController@index method?

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

medium

A. /admin/dashboard

B. /admin

C. /dashboard

D. /dashboard/admin

Solution

1. Step 1: Understand prefix effect on route URL

   The prefix 'admin' adds '/admin' before all routes inside the group.

2. Step 2: Combine prefix and route path

   The route path is 'dashboard', so full URL is '/admin/dashboard'.

3. Final Answer:

   /admin/dashboard -> Option A

4. Quick Check:

   Prefix + route path = full URL [OK]

Hint: Add prefix before route path for full URL [OK]

Common Mistakes:

• Ignoring prefix and using only route path
• Reversing prefix and path order
• Assuming prefix replaces route path

4. Identify the error in this Laravel route prefix usage:

Route::prefix('api', function () {
    Route::get('users', [UserController::class, 'index']);
});

medium

A. Missing ->group() method after prefix()

B. Prefix should be an array, not a string

C. Route::get() cannot be used inside prefix()

D. UserController::class is not valid here

Solution

1. Step 1: Check prefix() usage

   The prefix() method requires chaining with group() to define routes inside.

2. Step 2: Identify missing group() call

   Here, prefix('api') is called with a function directly, which is invalid syntax.

3. Final Answer:

   Missing ->group() method after prefix() -> Option A

4. Quick Check:

   prefix() must be followed by ->group() [OK]

Hint: Always chain ->group() after prefix() [OK]

Common Mistakes:

• Passing closure directly to prefix()
• Using array instead of string for prefix
• Misplacing route definitions outside group

5. You want to create a route group with prefix api/v1 and middleware auth:sanctum. Which of the following is the correct way to do this using chained prefix() and middleware() methods in Laravel?

hard

A. Route::group(['prefix' => 'api/v1', 'middleware' => 'auth:sanctum'], function () {
Route::get('profile', [ProfileController::class, 'show']);
});

B. Route::middleware('auth:sanctum')->prefix('api/v1', function () {
Route::get('profile', [ProfileController::class, 'show']);
});

C. Route::prefix('api/v1')->middleware('auth:sanctum')->group(function () {
Route::get('profile', [ProfileController::class, 'show']);
});

D. Route::group('api/v1')->middleware('auth:sanctum')->group(function () {
Route::get('profile', [ProfileController::class, 'show']);
});

Solution

1. Step 1: Understand chaining of prefix and middleware

   Laravel allows chaining prefix() and middleware() before group() to apply both settings.

2. Step 2: Check each option's syntax

   Route::group(['prefix' => 'api/v1', 'middleware' => 'auth:sanctum'], function () { Route::get('profile', [ProfileController::class, 'show']); }); uses array syntax, not chained methods. Route::prefix('api/v1')->middleware('auth:sanctum')->group(function () { Route::get('profile', [ProfileController::class, 'show']); }); correctly chains prefix() and middleware() then calls group(). Route::middleware('auth:sanctum')->prefix('api/v1', function () { Route::get('profile', [ProfileController::class, 'show']); }); incorrectly passes closure to prefix(). Route::group('api/v1')->middleware('auth:sanctum')->group(function () { Route::get('profile', [ProfileController::class, 'show']); }); misuses group() twice with wrong parameters.

3. Final Answer:

   Route::prefix('api/v1')->middleware('auth:sanctum')->group(function () { Route::get('profile', [ProfileController::class, 'show']); }); -> Option C

4. Quick Check:

   Chain prefix and middleware before group() [OK]

Hint: Chain prefix() and middleware() before group() [OK]

Common Mistakes:

• Passing closure directly to prefix() or middleware()
• Using group() twice incorrectly
• Mixing array and method chaining syntax