-
Notifications
You must be signed in to change notification settings - Fork 26k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reverse proxy problems. #60956
Comments
Facing similar issues with nginx and nextjs 14.1.0 |
Duplicate? Removing trailing / fixed my issue |
I don't think this is related to my case as I don't have any trailing / in any of the settings. |
After looking into it more closely, I've noticed something unusual. Even the default application returns a 404 error, but the issue is more complex. We receive a valid index response, which includes references to subsequent scripts and other elements, so the responses themselves appear valid. However, something occurs subsequently, and Next.js sets the status of response to 404. The only explanation I can think of is that there might be an issue with invalid headers. Could this be the reason Next.js is marking the request as 404? But that's just a wild guess. |
do the scripts in the index all have the appropriate basePath prepended? |
Yes, it does, but I have noticed that when I go to the default path, Next.js starts building the not-found page, which seems weird. |
I also have this issue.. |
Link to the code that reproduces this issue
https://github.com/zZHorizonZz/nextjs-routing
To Reproduce
Current vs. Expected behavior
Current behavior works like this:
The expected behavior is this should probably route and return the correct files. I found a related discussion to this here
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router, Routing (next/router, next/navigation, next/link)
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local)
Additional context
No response
The text was updated successfully, but these errors were encountered: