Solved

Browser doesn't like https://domainname.com but accepts https://www.domainname.com

Posted on 2011-03-03
4
471 Views
Last Modified: 2012-05-11
We have installed a dedicated SSL certificate (our web host did on our shared web site) for our www.domainname.org. When folks visit https://www.domainname.org they view the site in secure mode no problem.

BUT - there are some google links to our site that link to https://domainname.org (without the www prefix). When users click on that link, they get a security warning from their browser stating that the site was set up for www.domainname.org.

Why is this happening? I understand that the common name assigned to an SSL means that is the specific address that it is for. But I am able to go to my own local web server where I installed a dedicated SSL and I can go to either https://www.mydomain.com or https://mydomain.com and I don't get a security warning.

Why do users clicking on the google link get the security error, but I don't when I go to my local site in SSl mode? Is it because they are clicking on a link, vs. my manually typing it in my browser? That is the only difference I can make out.

Any thoughts?
0
Comment
Question by:rascal
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 83

Accepted Solution

by:
Dave Baldwin earned 500 total points
ID: 35034016
Your second paragraph Is the answer but here is an explanation: http://nayyeri.net/ssl-certificates-and-www-prefix-on-domain-names
0
 
LVL 1

Author Comment

by:rascal
ID: 35038973
Thanks DaveBaldwin,

The answer is contained in that post: some SSL issuers provide SSL certificates that work both WITH and WITHOUT the www. prefix, and at no extra charge. It's just part of the SSL certificate they generate.

For example, the SSL cert I got from Thawte works this way - it will work both with and/or without the www. prefix.

The problem SSL cert in this case was issued by SecureTrust and it requires the EXACT name - so if the SecureTrust certificate was issued as www.domainname.com, then that is the EXACT name that must be used.

Lesson learned - be sure you find out from the issuer whether the SSL certificate will work both WITH AND WITHOUT the www prefix - like Thawte does.
0
 
LVL 1

Author Closing Comment

by:rascal
ID: 35038981
Thanks Dave,
See my note above for more details.
0
 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 35039001
You're welcome and thanks for the points.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

So you need a certificate so you can offer SSL encryption.  But which one should you get?  There are so many choices out there! Here is a generic overview of the main types of SSL certificates sold by the majority of commercial Certification Auth…
SSL stands for “Secure Sockets Layer” and an SSL certificate is a critical component to keeping your website safe, secured, and compliant. Any ecommerce website must have an SSL certificate to ensure the safe handling of sensitive information like…
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question