Repository navigation
Doc: Clarify request context handling in UseStatusCodePagesWithReExecute (#34070) - #37818
Merged
guardrex merged 1 commit intoOct 9, 2026
Conversation
guardrex
approved these changes
Oct 9, 2026
guardrex
left a comment
guardrex
left a comment
Collaborator
There was a problem hiding this comment.
Yes! All true! Thanks again, @SkyDevLab! 🎸
I love seeing the issue count go down so rapidly on this repo! 🤩
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Clarify that UseStatusCodePagesWithReExecute modifies only the request path (clearing route data) while preserving original request data such as HTTP method, headers (including referrer), and items on HttpContext.Request. Also note that original path and query details are accessible via IStatusCodeReExecuteFeature.
Fixes #34070
Internal previews
Build report