[legacy-framework] use decodeURIComponent for router.query.next during page authentication redirect #2114
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.
I ran into an issue where my
Page.authenticate = { redirectTo: "/login" }
was not working as expected. The initial page washttp://localhost:3000/page-i-refreshed
and the redirect URL washttp://localhost:3000/login?next=%2Fpage-i-refreshed
(this is OK so far). But after I logged in, the URL changed tohttp://localhost:3000/%2Fpage-i-refreshed
instead of back tohttp://localhost:3000/page-i-refreshed
which generated a 404.What are the changes and their implications?
Use
decodeURIComponent
on therouter.query.next
path beforerouter.push
Update
blitz generate
templateUpdate default login example
Checklist