Getting 302s on client side navigation causing full page redirects and failure to find the pages #82455
Unanswered
patricktruong-cb
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Was wondering if anyone has ever has this issue.
We have deployed an application to production and this only happens in production.
The router using next/router and just page routes attempts to do a redirect to say
/next-page
just a simplerouter.push('next-page')
but the page is not found and the next js app does a 302 redirect can be seen in the docs of the network tab.Has anyone run into this issue because it is very hard to debug as I am unable to repo it locally
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions