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

Amplify redirects pages by appending build number in URL #1982

Closed
4 tasks done
ghost opened this issue Jun 21, 2021 · 4 comments
Closed
4 tasks done

Amplify redirects pages by appending build number in URL #1982

ghost opened this issue Jun 21, 2021 · 4 comments
Labels
archived This issue has been locked.

Comments

@ghost
Copy link

ghost commented Jun 21, 2021

Before opening, please confirm:

App Id

d2ql035tgxn6tg

Region

eu-west-1

Amplify Console feature

Build settings, Redirects

Describe the bug

I have an Angular app hosted by Amplify that is receiving rewrites for requests to non-existent pages that include an Amplify build number, even when no rewrite rules are created. This appears to be a recurrence of #405 .

Expected behavior

I would expect that the non-existent page to keep the same URL while providing a 403 or 404 rather than attempt to redirect it to a URL including the build number.

Reproduction steps

  1. Attempt to visit a known, non-existent path, e.g., https://<branchname>.<appid>.amplifyapp.com/assets/images/does-not-exist.png
  2. Observe the URL be redirected to include the Amplify build number, e.g., https://<branchname>.<appid>.amplifyapp.com/0000000001/assets/images/does-not-exist.png

Build Settings

No response

Additional information

Originally stems from this conversation on the AWS Amplify Discord https://discord.com/channels/705853757799399426/717110260057374720/856515177935011860

@github-actions
Copy link

Hi 👋, thanks for opening! While we look into this...

If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.

Lastly, please make sure you've specified the App ID and Region in the issue!

@calavera
Copy link
Contributor

This problem was resolved already according to this other issue: #405 (comment)

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

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.

@github-actions
Copy link

This issue has been automatically locked.

@github-actions github-actions bot added the archived This issue has been locked. label Jun 21, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked.
Projects
None yet
Development

No branches or pull requests

1 participant