You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
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
Attempt to visit a known, non-existent path, e.g., https://<branchname>.<appid>.amplifyapp.com/assets/images/does-not-exist.png
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
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
https://<branchname>.<appid>.amplifyapp.com/assets/images/does-not-exist.png
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
The text was updated successfully, but these errors were encountered: