-
Notifications
You must be signed in to change notification settings - Fork 19
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
API calls to _next/data fails with a 404 in standalone deployment with AWS Lambda #98
Comments
Hey!
What seems weird is that doubled |
That was a typo. The request is expected. Origin of request is the client. When there is a client side navigation within the app on the same route ( but on a different query string parameter ), client makes a request to getServerSideProps in the form of /_next/data/buildId/index.json. However, it seems Lambda is not able to figure out what to make of it. Not a typo. Happened because I used carets |
I can spin up an example and share repo if that helps. I couldn't find much info on Next SSR Standalone + AWS Lambda but for your package's github. Let me know if that'd help in your investigation ( if you have time for this ofcourse ) |
@js-sapphire I tried replicating without much luck :/ could you try to share repo steps? |
Thanks @sladg |
Closing, inactive :) |
I am building an SSR application with Next 13 with standalone output. No basepath. And I am using Page Router.
We have certain places where we are doing client side navigation which is triggering an API call ( _next/data/buildId/index.json ) but it fails with a 404. Now, these requests are being sent to the Lambda but they fail and that results in a page refresh.
My questions were:
The text was updated successfully, but these errors were encountered: