SSL certificate with VeriSign does not work for non-www link, how to redirect the non-www url to www.sitename.com

Hello,

Our website is hosted on windows server 2003 by a hosting provider offsite. We have a SSL certificate purcahsed from VeriSign for www.sitename.com, but when a client types in http://sitename.com the SSL certificate error is encountered as the site is not registered under http://sitename.com.

What can be the possible solution to make the SSL certificate work for http://sitename.com as per my knowledge it would be either to redirect the http://sitename.com to www.sitename.com. If this is true then can someone guide me on what we have to do to accomplish this. We have asked our hosting provider and they have no clue on what to do.

The next thing would be to buy a new certificate for http://sitename.com but is there any other solution that can make it work without spending all the extra bucks.

Thanks in advance
Swapna
VisanowAsked:
Who is Participating?
 
mrcoffee365Commented:
Normally people redirect from the http://domain.com to https://www.domain.com .  That way you only need one certificate for the www.domain.com .

There are a couple of ways to handle it in IIS.  One is to put a Javascript redirect in all of your header pages.

Another is to set up an IIS site listening for http://domain.com and redirect it to your site https://www.domain.com .

Another is to set up your IIS www.domain.com to only allow https.  Then put in a custom error for 403 to redirect the user to https://www.domain.com .

These links have discussions of these various solutions:
http://support.microsoft.com/kb/839357
http://www.experts-exchange.com/Networking/Misc/Q_21256905.html
http://weblogs.asp.net/pwilson/archive/2004/12/23/331455.aspx
The following page is a good discussion of options, but the main server wasn't answering, so this is the Google cached page:
http://64.233.169.104/search?q=cache:_tJvfeonTtwJ:blog.opsan.com/archive/2005/04/17/395.aspx+iis+http+redirect+to+https&hl=en&gl=us&strip=1
This is the real link for it:
http://blog.opsan.com/archive/2005/04/17/395.aspx
0
 
meverestCommented:
if your certificate matches www.sitename.com and you want to be able to access https://sitename.com then you have no choice than to buy a new certificate.  No manner of redirection, forwarding or site wrapping will give you the same (or even remotely similar) result.

you can get a lot cheaper than verisign (if the $$ are the problem) - just search for "cheap ssl certificate" in your favorite search engine.

Cheers.



0
 
VisanowAuthor Commented:
I see that many sites like amazon,google n many others when typed http://yahoo.com they automatically redirect to www.yahoo.com, isnt there any a way to do that?
0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
meverestCommented:
sure there is.  BUT you need a certificate to cover every domain - either many specific certificates, or a suitable wildcard cert.

Cheers.
0
 
meverestCommented:
>> Normally people redirect from the http://domain.com to https://www.domain.com .  That way you only need one certificate for the www.domain.com

that is still no help in this case - you will STILL need two certificates, else one (or the other) will pop a 'security warning'

Cheers.
0
 
mrcoffee365Commented:
meverest -- yes, you have been right all along, if Visanow wishes to have
https://domain.com 
serve with a certificate, then he would need to get a certificate for that domain.

However, most people who run Web servers with SSL only get 1 certificate for the main domain, say www.domain.com, and redirect with various mechanisms when users need to go to the secure connection.

My concern is that you made it sound as if Visanow was required to get another certificate, when in fact that is rarely the case.
0
 
meverestCommented:
>> My concern is that you made it sound as if Visanow was required to get another certificate, when in fact that is rarely the case.

I don't understand you point.  The facts are plain.  He *has* a certificate for www.domain.com.  He *wants* to be able to use https://domain.com

Solution: He needs a cert for domain.com

The questions:

1.  What can be the possible solution to make the SSL certificate work for http://sitename.com

answer, get a new cert.

2.  but is there any other solution that can make it work without spending all the extra bucks

answer, no.  but if extra bucks are the problem, choose someone other than verisign.

Cheers.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.