fix: RedirectException no longer defaults to a 302 status code - #10500
Merged
paulbalandan merged 1 commit intoAug 28, 2026
Merged
Conversation
paulbalandan
added
the
bug
paulbalandan
force-pushed
the
redirect-exception-code-regression
branch
from
August 28, 2026 16:13
b536225 to
29e8651
Compare
michalsn
approved these changes
Aug 28, 2026
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.
Description
Adds a regression fix to #10465. #10465 dropped
RedirectException's$codedefault, so a barenew RedirectException($uri)now throws instead of redirecting with 302. Restores the default via a shared constant.Checklist: