Fix 500 errors when handling unsafe redirects#6682
Merged
mitchellhenke merged 2 commits intomainfrom Aug 3, 2022
Merged
Conversation
mitchellhenke
commented
Aug 2, 2022
mitchellhenke
changed the title
mdiarra3
approved these changes
Aug 3, 2022
mitchellhenke
force-pushed
the
mitchellhenke/fix-unsafe-redirect-500
branch
from
80d78a9 to
7efdcb4
Compare
changelog: Bug Fixes, Security, Fix 500 error when handling unsafe redirects
Co-authored-by: Zach Margolis <zachmargolis@users.noreply.github.com>
mitchellhenke
force-pushed
the
mitchellhenke/fix-unsafe-redirect-500
branch
from
7efdcb4 to
d8f31ee
Compare
Merged
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
3 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.
Seeing a couple of 500s in staging and int that appear to be partly a result of the Rails 7 upgrade