Middleware parameters in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Laravel middleware receive parameters?

Consider a Laravel middleware that accepts parameters. How are these parameters passed when defining middleware in routes?

Laravel

Route::get('/profile', function () {
    // ...
})->middleware('role:admin,editor');

A Parameters are passed as an array in the middleware method call.

B Parameters are passed as a comma-separated string after a colon in the middleware name.

C Parameters are passed as query parameters in the URL.

D Parameters are passed via HTTP headers automatically.

💡 Hint

Think about how the middleware name is written in the route definition.

In Laravel, middleware parameters are passed as a comma-separated list after a colon in the middleware name string. For example, 'role:admin,editor' passes 'admin' and 'editor' as parameters.

❓ state_output

intermediate

What is the output of middleware parameter parsing?

Given this middleware handle method, what will be the value of $roles when the middleware is called with role:admin,editor?

Laravel

public function handle($request, Closure $next, ...$roles)
{
    return response()->json($roles);
}

A []

B ["role:admin", "editor"]

C ["admin,editor"]

D ["admin", "editor"]

💡 Hint

Look at how the parameters are captured using the spread operator ...$roles.

The middleware receives parameters after the request and next arguments. Using ...$roles collects all parameters into an array. So, 'admin' and 'editor' become elements of the $roles array.

📝 Syntax

advanced

Identify the syntax error in middleware parameter usage

Which option contains a syntax error when defining middleware with parameters in Laravel routes?

Laravel

Route::get('/dashboard', function () {
    // ...
})->middleware('auth', 'role:admin');

A ->middleware('auth', 'role:admin')

B ->middleware('role:admin')

C ->middleware(['auth', 'role:admin'])

D ->middleware('auth')->middleware('role:admin')

💡 Hint

Check the method signature of middleware() in Laravel routing.

The middleware() method accepts either a single string or an array of middleware names. Passing multiple string arguments like ('auth', 'role:admin') causes a syntax error. Use an array or chain calls instead.

🔧 Debug

advanced

Why does this middleware parameter not work as expected?

Given this middleware handle method, why does passing role:admin,editor not restrict access properly?

Laravel

public function handle($request, Closure $next, $role)
{
    if (! $request->user()->hasRole($role)) {
        abort(403);
    }
    return $next($request);
}

A Only the first parameter 'admin' is captured; 'editor' is ignored because $role is a single variable.

B The middleware does not receive any parameters because of missing type hint.

C The abort(403) call is misplaced and never executes.

D The handle method should return a boolean, not a response.

💡 Hint

Consider how multiple parameters are captured in the method signature.

The handle method only accepts one parameter $role. When multiple parameters are passed, only the first is assigned. To capture all parameters, use ...$roles to collect them into an array.

🧠 Conceptual

expert

How to access middleware parameters in a Laravel middleware class?

Which code snippet correctly accesses multiple middleware parameters passed as role:admin,editor in a Laravel middleware class?

A public function handle($request, Closure $next, $role1, $role2) { /* use $role1 and $role2 */ }

B public function handle($request, Closure $next, $roles) { $roles = explode(',', $roles); }

C public function handle($request, Closure $next, ...$roles) { /* use $roles array */ }

D public function handle($request, Closure $next) { $roles = func_get_args(); }

💡 Hint

Think about how PHP collects variable-length argument lists.

Using ...$roles collects all middleware parameters into an array automatically. Option C tries to parse a single string, which Laravel does not pass. Option C requires exact parameter count, which is inflexible. Option C does not correctly separate parameters.