Skip to content
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

Redirection problem with Nextjs application deployed on aws s3 and cloundfront as static application #13810

Closed
2 tasks done
saharJ95 opened this issue Jun 6, 2024 · 2 comments
Labels
pending-triage Issue is pending triage

Comments

@saharJ95
Copy link

saharJ95 commented Jun 6, 2024

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

21.6.1

Amplify CLI Version

12.12.1

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Create s3 bucket and link it with cloudfornt (custom domain)

Describe the bug

Redirection problem with Nextjs application deployed on aws s3 and cloundfront as static application

The Apps work fine but when we reload the route except index.html page it lands to home page i.e. index.html

apps/user/list ---> after reload ---> apps/

Expected behavior

should land to desired url

Reproduction steps

login to app
route to other routes
refresh

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@saharJ95 saharJ95 added the pending-triage Issue is pending triage label Jun 6, 2024
@ykethan
Copy link
Member

ykethan commented Jun 11, 2024

Hey @saharJ95, thank you for reaching. This appears to be a behavior with the NextJs application, refer to this thread vercel/next.js#10522 providing additional information on this behavior.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

2 participants