Issue Feature Under Review Quiet

#111179Run Extbase action invocation, #[Authorize] and #[RateLimit] through an inner middleware stack

Alexander Schnitzler 10/20/26, 15:20 updated 11/04/26, 10:01

Description

After argument mapping and validation, ActionController::callActionMethod() handles validation errors, #[Authorize] and #[RateLimit] in fixed code; extensions cannot hook in between with access to the mapped arguments.

Proposal: a second stack “extbase-action” runs after mapping/validation inside the controller. The controller hands over an invocation object (controller, action, Arguments, prepared values, closures for the action and errorAction so protected methods keep working). Core registers three middlewares in today’s order: argument validation (short-circuit to errorAction), authorize, rate limit; the kernel dispatches BeforeActionCallEvent and calls the action. Semantics stay as today (rate limit is still not consumed on validation errors).

Breaking: ActionController::performAuthorizationChecks(), handleRateLimit(), injectRateLimitRegistry(), injectAuthorizeRegistry() are removed; subclasses overriding them must move to middlewares.

Reviews 2

History 15