1 Answer
- Newest
- Most votes
- Most comments
0
You cannot do an HTTPS redirect like that - as the first TLS connection would still be to a URI that is not in the subject alternative names of the certificate.
If you have a domain structure as follows:
www.sub-domain.domain.com, but also want to have a domain hosted at
sub-domain.domain.com`
Then the www
portion is another sub-domain, so your certificate needs to include that as well. You wold therefore need a certificate containing at least the following names.
sub-domain.domain.com
www.sub-domain.domain.com
And you are right - some browsers will support *.*.domain.com
in subject alternate names (Chrome for instance), but many CAs will not allow you to issue a certificate like that - thus you can do the following.
*.sub-domain.domain.com
*.other-sub-domain.domain.com
Relevant content
- asked 3 months ago
- asked 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
That you Max. Can the cert be for domain, .domain, and www..domain or do I need to be specific about the sub-domains?