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 Console redirects to wrong url when trailing slash required #405
Comments
Hi @idrisov-ri we cut a ticket in our customer oncall backlog, will investigate your issue later. Thank you for understanding. |
Hi @idrisov-ri , Thank you for reporting. I cut a ticket in our team backlog. We will working on investigating a fix! |
@Joycehao19 +1 for this problem to be fixed. Btw, is there any workarounds to redirect url without trailing slash to one with trailing slash? |
I add myself to this problem, but for me the problem is as follows: But if for some reason I refresh, either by pressing F5 or pressing the icon on the browser, then I get the I do have a single redirect setup due to my app being a SPA build on VueJS: My application id is |
Forget my initial reply, I just followed the info on https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#redirects-for-single-page-web-apps-spa and now its redirecting correctly. The only heads up is to copy paste the Regex using the Open text editor option after you clicked Edit on the Rewrites and redirects page, that way you are sure you didn't copy some undesired space. |
Hi, I'm also having this issue. Will there be a fix soon? |
Just to add some info, I've noticed that the problem doesn't happen on build previews, only on main deployments. |
this works for me |
This has been open for a long time. When is this issue coming out of the backlog and being worked on? |
Same issue here! Cannot accept url query params because of the trailing dash, it cleans everything on the query |
Fixed it by changing my "Rewrites and Redirects" rules. The only one I left was this one: |
The issue with build numbers being appended to redirects has been resolved. I am closing out this issue, but please open a new one if anyone continues to have issues. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Not sure this is right place for my question.
From AWS Amplify documentation:
In App we are working at now the second scenario is not true.
When user inputs
/about
(no trailing slash in the end)and needed to be redirected to/about/
(have trailing slash in the end), instead he is being redirected to a url similar to something like/0000000030/about/
. Where the0000000030
part of the url seems to be a Build ID of AWS Amplify App.This url not exists so user get 403 response status with
AccessDenied
XML error message.My question is, is it desired behavior or is it a bug?
If it is a bug what can we do to make it work as desired?(
/about
, is rediricted to/about/
, not to/0000000030/about/
)By the way, there are no Rewrite or Redirect rules set up in our Amplify Console App.
thanks in advance!
The text was updated successfully, but these errors were encountered: