aws-amplify / aws-amplify/amplify-hosting
AWS Amplify - Rewrites Redirects and html extensions
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
**Please describe which feature you have a question about?**
Rewrites/Redirects
**Provide additional details**
When deployed, I have urls ending in ```/folder/folder/file.html``` and also many ending in ```/folder/folder/index.html```. That last one loads fine, it's the first one with the .html extensions that seem to be rewritten, as shown in the address bar as ```/folder/folder/file/``` which does not exist. What rewrite rule(s) can make Amplify show both of these properly? I read if I re-name my file.html to /file/index.html it will work but I do not want to do that if a simple rewrite works.
**What AWS Services are you utilizing?**
Amplify
**Provide additional details e.g. code snippets**
See above
Contributor guide
Research direction
The issue names no repository files, tests, or code entry points; it describes an AWS Amplify Hosting rewrite/redirect question. Start by reading the Amplify Hosting rewrite and redirect documentation and checking the deployed configuration. Done would mean both `.html` URLs and `index.html` URLs load as intended, but the issue does not specify a code change or a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100