aws-amplify / aws-amplify/amplify-hosting

Non-www redirect to www not working for main domain

Open
#2,948 1 comment 0 reactions 0 assignees View on GitHub
custom-domain question
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked the [custom domains troubleshooting guide](https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

djkqpxwstmtk8

### Region

ap-south-1

### Step

www redirect from non-www

### Status

HTTP Status: 404 (not found)

### Issue or question

Non-www URLs keeps going to an HTTP Status: 404 (not found) page, when a sub-domain is configured it works fine, however does not work with the base domain.

### Error message

HTTP Status: 404 (not found)

### Additional information

Screenshot 2022-08-25 at 9 22 46 AM

Contributor guide

Open the contributing guide

Research direction

The issue names no repository files, tests, or code entry points. Start by reproducing the non-www request for the reported app in ap-south-1 and compare it with the working subdomain behavior; done means the base domain redirects successfully to www instead of returning HTTP 404.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.