Make UseStatusCodePagesWithReExecute clear Endpoints #14531
Merged
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.
#13715 There was a regression when switching to Endpoint based routing. When the status code component tries to re-execute the pipeline there is some state that needs to be cleared first such as the endpoint, otherwise the request will be routed to the old endpoint again.
Normally a middleware would do it's own cleanup (e.g. routing), but that significantly impacted the perf in the case of routing.
In 3.0 @NTaylorMullen Fixed this in UseExceptionHandlerWithReExecute but we missed UseStatusCodePagesWithReExecute.
1f0641f#diff-abb2b51ad2d2d988debc78909b2674d9
FYI: I split the test files for exception handler and status code handler.