-
Notifications
You must be signed in to change notification settings - Fork 116
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
Fix broken region based redirects #3955
Comments
Thanks for the report. We have prioritized a fix and will let you know when its rolled out. |
@mbacchi we rolled out a fix. Can you verify please? |
Thanks for the update @swaminator. Unfortunately this doesn't seem to fix the issue for me, I'm still receiving traffic from RU. |
@swaminator - is there an ETA for a fix here? This issue is blocking our team from launching a critical feature for our customers |
@swaminator I believe an update would be fitting. This is a 6 week old ticket that reported a longstanding issue for a feature you have claimed support in your product for years. Doesn't seem to me that this is "working as intended". Please let us know if and when a solution is coming. Meantime, I'm working on a replacement for amplify using an S3 hosted site fronted by a Cloudfront distribution that I control myself. Wish it didn't come to this but weeks between responses is sorta unacceptable. |
@mbacchi apologies for the delay. We pushed another fix can you try re-deploying your app? |
@swaminator Is it necessary to re-deploy? Will it not just work with my existing deployment? |
Yes please redeploy. |
I redeployed on Nov 19 and since then there have been no hits from the redirected country. |
Before opening, please confirm:
Amplify Hosting feature
Redirects
Is your feature request related to a problem? Please describe:
The Amplify documentation indicates that users can redirect based on region. This was working but is no longer. With the redirect below my site is serving requests requests from RU:
Please address this issue.
Describe how you'd like this feature to work
Redirect requests as the documentation describes.
The text was updated successfully, but these errors were encountered: