aws-amplify / aws-amplify/amplify-hosting
403 Access Denied when location query param is used on direct navigation
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
I got 403 Access Denied when use the query param '?location' in my Amplify Hosted App
**To Reproduce**
Steps to reproduce the behavior:
1. Go to https://my-domain.com/?location or https://my-domain.com/signup?location or any route with the query param '?location'
2. Get 403 error
**Expected behavior**
It should show the page as it is
**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: Windows
- Browser: Chrome
- Version 88.0.4324.190
Contributor guide
Research direction
Start by reproducing the 403 using the reported direct URLs, including the root and /signup routes with the location query parameter, and inspect the Amplify Hosting configuration and request path involved. Done means those direct navigations serve the expected page instead of returning 403, while normal routes continue to work.
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
- Mostly clear
- Newbie friendliness
- 35/100