Do not apply filters when RouteExecutor decides not to handle an error #6745
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For certain errors (
isIgnorable
), theRouteExecutor
decides not to write a response for the error, and returns an empty flux. However, without this patch, theRoutingInBoundHandler
would still apply filters. For example, the micronaut-security filter will check access permissions for the error request, even though those routes would never be executed anyway (RouteExecutor
decided not to). That filter may then return a response.This patch adds a short-circuit check for these 'closed connection' errors to
RoutingInBoundHandler
, and avoids running downstream processing altogether.Fixes #6723