: Www.mydomain.com secure but not mydomain.com? Possible Duplicate: www.mydomain.com secure but not mydomain.com? Hi We've got our website running and https / ssl works just great. EXCEPT
Possible Duplicate:
mydomain.com secure but not mydomain.com?
Hi
We've got our website running and https / ssl works just great.
EXCEPT
when users enter www.mydomain.com and then enter the secure area and get directed to www.mydomain.com it works fine.
But when users enter just mydomain.com and then enter the secure are and get directed to mydomain.com they get a warning about the certificate being from a website called "www.mydomain.com" while they're trying to enter "mydomain.com" ....
Does our SSL cert not cover both mydomain.com and mydomain.com? Are we suppose to buy TWO certs, on for each?? Surely not?
Any help or pointers to the standard way of doing things like this would be great.
We're using Apache HTTPD to forward requests to Tomcat webapps. Apache is taking care of all the SSL connections.
More posts by @Yeniel560
1 Comments
Sorted by latest first Latest Oldest Best
Make example.com redirect to www.example.com.
To answer your remaining questions, no - SSL certificate verification steps covers only the configured name. It is possible to obtain a certificate that covers more than one name; and is supported in all modern browsers.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.