You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This documents the request query passing behavior of redirects to help avoid confusion.
## Documentation / Examples
- [x] Make sure the linting passes
Closes: #27194
flybayer
pushed a commit
to blitz-js/next.js
that referenced
this issue
Aug 19, 2021
This documents the request query passing behavior of redirects to help avoid confusion.
## Documentation / Examples
- [x] Make sure the linting passes
Closes: vercel#27194
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 28, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the Bug
Problem creating 301 redirects
Expected Behavior
when creating a redirect it passes the parameters to the destination by default, but the expected result is a url without parameters.
To Reproduce
Just putting the following code in next.config.js
The redirect from /lamps.html?p=1 makes it to /lamps?p=1 and the expected result is /lamps
The text was updated successfully, but these errors were encountered: