Problems with routes and 404 page on Gatsby site in AWS Amplify

[anatolzak]

I have created a multi-page site with gatsby.js deployed on Amplify.

When I go to any page other than index.html, it shows me my 404.html and then after a few seconds, it shows the actual page I should see for that route.

Obviously there is something wrong with that. I deployed the same site with Netlify and that doesn't happen there.

Here are my Rewrites and redirects:

[ohlr]

</index\.html/> -> /404.html

[anatolzak]

@ohlr that worked by it doesn't keep query params.

[ohlr]

there is a whole discussion here #70..

[fpsoriano]

I have the same problem.

https://www.apresentar.me/fabricio => does not work
https://www.apresentar.me/fabricio/ => works.

Did you find a solution?

[anatolzak]

@fpsoriano I haven’t yet found a solution. I have been using Netlify instead because everything works perfectly with them.

I wish deploying to amplify didn’t include having to figure out weird bugs that simply aren’t supposed to be part of the platform :(

[cslogan-red]

As noted by @ohlr the solution in #70 is currently the accepted solution for 404 rewrite behavior. As far as query string params, the target address currently only supports path based params used by most router frameworks, not the transposition of a query string, IE, the below is valid:

Source is: /docs?id=<resourceId>&hat=<hat>
Target is: /documents/<resourceId>/<hat>

But the following is not currently directly supported ( see #97 )

Source is: /docs?id=<resourceId>&hat=<hat>
Target is: /documents?id=<resourceId>&hat=<hat>

That said, as others have mentioned in #97 , you can use a trailing slash with a wildcard (the trailing slash is required) in the source to redirect everything (including anything you want preserved in the query string) from one path to another:

Source is: /docs/<*>
Target is: https://myurl.com/<*>

Closing this as a duplicate of #70 and #97, please follow those issues for updates and let us know if you have any further questions in either of those issues, thanks!

[github-actions]

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.