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
We've just recently deployed the latest stacks for the AWS retail demo store, and it looks great, however we notice that we can't refresh any pages outside of the home page.
Steps to reproduce:
Deploy the Retail Demo Store to a new AWS account
Browse to the generated url for the retail demo store
Browse to one of the featured products
Refresh the current page
Expected behaviour:
Product page is reloaded successfully
Actual behaviour:
An "Access Denied" error is shown to the user
Note that this also happens on other pages - e.g if the auth page is refreshed.
The text was updated successfully, but these errors were encountered:
Hi!
Thanks for raising this, can you confirm that you are using a recent version of the Retail Demo Store? Was it a fresh install ?
We deployed large changes on moving to cloudfront https + api gateway, full on HTTPS recently (see PR #451)
The issue is due to the frontend being a SPA. When you perform a request at the root / homepage, then CloudFront is configured to request the index.html. However, if you request any other path, then an attempt is made to retrieve the resource, which doesn't actually exist (it's just a route within the SPA).
You can configure the CloudFront distribution for the Web-ui to return a Customer Error Response:
HTTP Error Code: 403
Response Page path: /index.html
Http Response Code: 200
We'll look to have this pre-configured as part of deployment
Hi team,
We've just recently deployed the latest stacks for the AWS retail demo store, and it looks great, however we notice that we can't refresh any pages outside of the home page.
Steps to reproduce:
Deploy the Retail Demo Store to a new AWS account
Browse to the generated url for the retail demo store
Browse to one of the featured products
Refresh the current page
Expected behaviour:
Actual behaviour:
Note that this also happens on other pages - e.g if the auth page is refreshed.
The text was updated successfully, but these errors were encountered: