AWS amplify documentation change
Summary
Added documentation about unsupported path components in domain redirects
Security assessment
The change clarifies a technical limitation (path components in redirects being ignored) but does not address a security vulnerability or introduce security documentation. It improves accuracy of feature behavior documentation.
Diff
diff --git a/amplify/latest/userguide/troubleshooting-custom-domains.md b/amplify/latest/userguide/troubleshooting-custom-domains.md index a54cf74ab..2e8e78676 100644 --- a//amplify/latest/userguide/troubleshooting-custom-domains.md +++ b//amplify/latest/userguide/troubleshooting-custom-domains.md @@ -5 +5 @@ -I need to verify that my CNAME resolvesMy domain hosted with a third-party is stuck in the Pending Verification stateMy domain hosted with Amazon Route 53 is stuck in the Pending Verification stateMy app with multi-level subdomains is stuck in the Pending Verification stateMy DNS provider doesn't support A records with fully qualified domain namesI get a CNAMEAlreadyExistsException errorI get an Additional Verification Required errorI get a 404 error on the CloudFront URLI get SSL certificate or HTTPS errors when visiting my domain +I need to verify that my CNAME resolvesMy domain hosted with a third-party is stuck in the Pending Verification stateMy domain hosted with Amazon Route 53 is stuck in the Pending Verification stateMy app with multi-level subdomains is stuck in the Pending Verification stateMy DNS provider doesn't support A records with fully qualified domain namesI get a CNAMEAlreadyExistsException errorI get an Additional Verification Required errorI get a 404 error on the CloudFront URLI get SSL certificate or HTTPS errors when visiting my domainPath components not supported in domain redirects @@ -32,0 +33,2 @@ If you don't see a solution to your issue here, contact Support. For more inform + * Path components not supported in domain redirects + @@ -194,0 +197,4 @@ To reconnect your app to your custom domain, use one of the following procedures +## Path components not supported in domain redirects + +Domain redirects only match the hostname portion. Path components in domain-based source rules (e.g., `"https://domain.com/path"`) are not supported and will cause the rule to be ignored without error. For more information, see [Redirects and rewrites example reference](./redirect-rewrite-examples.html). +