Redirect that could work for any query string?

Question

{  
    "source": "/old/path?",  
    "target": "/new/path/?",  
    "status": "301",  
    "condition": null  
}  
  
Why doesn't this work?  
  
Edited by: WD40erik on Jul 9, 2019 6:57 PM

Accepted Answer

The redirect query string can contain multiple parameters but cannot be formatted as a single string param like you've listed there. Additionally, the target currently only supports path based URL's when using query strings (like those used with SPA routing frameworks, aka react-router, angular-router, etc).  
  
The following are valid redirects (the names are arbitrary):  
  
/docs?id=  
/documents/  
  
/docs?id=&nextId=&finalId=  
/documents///  
  
etc...  
  
Note that if any target is not a valid path within your app, the default redirect rule will redirect all invalid requests back to root.

Answer

Hi **WD40erik**,  
  
I have the same issue with multiple environments using GitFlow.  
  
We have **qa.example.com** and **dev.example.com** with zero code changes between the two. However, **qa.example.com** was deployed 3 days before **dev.example.com** and **qa** works as I expect.  
  
When navigating to **/dashboard** and **/dashboard/**, with or without a trailing slash on **qa** it works fine and renders the page. If you navigate to the **dev** subdomain without a trailing slash, **/dashboard** it redirects to **/dashboard/** with the appended trailing slash and removes any query parameters.  
  
This is super frustrating as there are no differences between the codebases and there are no **rewrites and redirects** rules set for the app. My only guess is that AWS Amplify Console changed its default routing/redirects within the past week or so. Hence **qa** subdomain was not affected, since it was deployed a few days earlier, and **dev** subdomain was affected by some Amplify Console code change.

Redirect that could work for any query string?

相關內容