Re: Do I really need a wild card certificate ?
- From: "Funkadyleik Spynwhanker" <youreallywantoemailmepunk?@winblows.gov>
- Date: Fri, 31 Mar 2006 08:09:41 -0600
"Bernard Cheah [MVP]" <qbernard@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OZKvFdIVGHA.5332@xxxxxxxxxxxxxxxxxxxxxxx
For starter, SSL cert bind to website level, you can't install cert on
virtual directory/file level, however you can control SSL requirement all
the way from site to directories or even file level....
Now, I don't get you on -> I can't get SSL working on external sites.
External site is your main site? http:// working but not https:// what do
you get when you browse under https ?
That sounds an awful lot like the network address translation in to the
local network is wrong.
Or that the IP on the cert is not bound to the IP that the router/firewall
is translating in or something.
Maybe if you posted all of the details of the DNS resolution and the IPs for
the devices someone could point out the error.
Likewise, check the port translation and the IPs. You might be sending port
80 (http) to some place else entirely, and port 443 (https) is the one that
is actually translated correctly.
.
- References:
- Re: Do I really need a wild card certificate ?
- From: Bernard Cheah [MVP]
- Re: Do I really need a wild card certificate ?
- From: Bernard Cheah [MVP]
- Re: Do I really need a wild card certificate ?
- Prev by Date: Re: Restricting IIS from serving static content
- Previous by thread: Re: Do I really need a wild card certificate ?
- Index(es):