Domain Name Mismatch

Hello,

I just started with certificates and SSL. I have a certificate for a
domain.com, installed on IIS and works fine if I try to access it
through https://domain.com. However, if I access it with www (https://
www.domain.com) I get Domain Name Mismatch. I do not want to buy
another certificate and was wondering if there is anything I could do
to automatically redirect to https://domain.com

I noticed something similar to what google does with gmail. There is
certificate warning on https://gmail.com but then get redirected to
https://www.google.com/gmail

https://gmail.com to https://www.google.com/gmail


please help.

Re: Domain Name Mismatch

Unless you use a "wildcard certificate" then certificates are specific to
hostnames. (As you have found out.)

To remedy this, you can use an asp - redirect (just search Google for "asp
ssl redirect" for examples), or , you could create a second web site using
IIS. That web site consists of an empty folder, it redirects (using IIS
redirect in the "home directory" tab) to the proper url without WWW, but
including the Https part.

Run that site on port 80, on the same IP with the "improper" hostnames, and
with "domain.com" on port 80.

Run the site with the certificate on port 81 (unused) and port 443 (the SSL
port).

The net effect will be visits to the site under improper hostname get
redirected to the proper one in https. Visits to the proper hostname in
http mode will get redirected to https. That will happen transparently
(mostly) to your users, and you can also not worry about if your URLs in
links and stuff are set to secured mode because users dont visit the site in
non secured mode.

And... of course for your next certificate, you know the hostname is pretty
important to be careful about.

wrote in message
news:1188493654.422056.141130@22g2000hsm.googlegroups.com...
> Hello,
>
> I just started with certificates and SSL. I have a certificate for a
> domain.com, installed on IIS and works fine if I try to access it
> through https://domain.com. However, if I access it with www (https://
> www.domain.com) I get Domain Name Mismatch. I do not want to buy
> another certificate and was wondering if there is anything I could do
> to automatically redirect to https://domain.com
>
> I noticed something similar to what google does with gmail. There is
> certificate warning on https://gmail.com but then get redirected to
> https://www.google.com/gmail
>
> https://gmail.com to https://www.google.com/gmail
>
>
> please help.
>

Re: Domain Name Mismatch

On Aug 31, 10:06 am, ".._.." <.....@yourmom.mil> wrote:
> Unless you use a "wildcard certificate" then certificates are specific to
> hostnames. (As you have found out.)
>
> To remedy this, you can use an asp - redirect (just search Google for "asp
> ssl redirect" for examples), or , you could create a second web site using
> IIS. That web site consists of an empty folder, it redirects (using IIS
> redirect in the "home directory" tab) to the proper url without WWW, but
> including the Https part.
>
> Run that site on port 80, on the same IP with the "improper" hostnames, and
> with "domain.com" on port 80.
>
> Run the site with the certificate on port 81 (unused) and port 443 (the SSL
> port).
>
> The net effect will be visits to the site under improper hostname get
> redirected to the proper one in https. Visits to the proper hostname in
> http mode will get redirected to https. That will happen transparently
> (mostly) to your users, and you can also not worry about if your URLs in
> links and stuff are set to secured mode because users dont visit the site in
> non secured mode.
>
> And... of course for your next certificate, you know the hostname is pretty
> important to be careful about.
>
> wrote in message
>
> news:1188493654.422056.141130@22g2000hsm.googlegroups.com...
>
> > Hello,
>
> > I just started with certificates and SSL. I have a certificate for a
> > domain.com, installed on IIS and works fine if I try to access it
> > throughhttps://domain.com. However, if I access it with www (https://
> >www.domain.com) I get Domain Name Mismatch. I do not want to buy
> > another certificate and was wondering if there is anything I could do
> > to automatically redirect tohttps://domain.com
>
> > I noticed something similar to what google does with gmail. There is
> > certificate warning onhttps://gmail.combut then get redirected to
> >https://www.google.com/gmail
>
> >https://gmail.comtohttps://www.google.com/gmail
>
> > please help.

thanks for the help!