I have a Default Site with port 443 for SSL.
If I have a secondary web site, that uses both 80 and 443 (the same ports)
but with a different header name, when starting this site I get an error
telling that port 443 is already in use, and that I should assign a diffent
number.
Is is possible to share the 443 port like I share the 80 port?
Thanks!
On Sep 26, 9:11 am, "Jazmin Gutierrez"
wrote:
> I have a Default Site with port 443 for SSL.
> If I have a secondary web site, that uses both 80 and 443 (the same ports)
> but with a different header name, when starting this site I get an error
> telling that port 443 is already in use, and that I should assign a diffent
> number.
>
> Is is possible to share the 443 port like I share the 80 port?
>
> Thanks!
You can share the SSL port using Host header only if you can use the
same SSL Server Certificate for ALL websites that want to share, and
you are using IIS6 on Windows Server 2003 SP1 or later.
This is a restriction of SSL, which does not multiplex endpoints using
Host headers because it operates at the TCP, not HTTP (where Host
headers exist) layer.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Ok.
Suppose I have site nº 1 with host header "www1.mydomain.com"
and site nº 2 with host header "www2.mydomain.com"
Can I have a wilcard certificate for *.mydomain.com?
Where should I install it?
Thanks!
"David Wang"
news:1190877162.022203.177650@k79g2000hse.googlegroups.com.. .
> On Sep 26, 9:11 am, "Jazmin Gutierrez"
> wrote:
>> I have a Default Site with port 443 for SSL.
>> If I have a secondary web site, that uses both 80 and 443 (the same
>> ports)
>> but with a different header name, when starting this site I get an error
>> telling that port 443 is already in use, and that I should assign a
>> diffent
>> number.
>>
>> Is is possible to share the 443 port like I share the 80 port?
>>
>> Thanks!
>
>
> You can share the SSL port using Host header only if you can use the
> same SSL Server Certificate for ALL websites that want to share, and
> you are using IIS6 on Windows Server 2003 SP1 or later.
>
> This is a restriction of SSL, which does not multiplex endpoints using
> Host headers because it operates at the TCP, not HTTP (where Host
> headers exist) layer.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
You can use whatever certificate you want. As long as the client will
recognize that certificate as valid for its intended host.
You install the SSL Certificate for each website that communicates
over SSL. There is nothing special here. It's just how SSL works.
In your example, you can have a single wildcard certificate for
*mydomain.com and install it in IIS website definition(s) for
www1.mydomain.com and www2.mydomain.com.
Or you can use a single certificate valid for www1.mydomain.com and
www2.mydomain.com. Or any other certificate that will be valid for the
host that it is supposed to represent.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Sep 27, 5:54 am, "Jazmin Gutierrez"
wrote:
> Ok.
> Suppose I have site n=BA 1 with host header "www1.mydomain.com"
> and site n=BA 2 with host header "www2.mydomain.com"
>
> Can I have a wilcard certificate for *.mydomain.com?
> Where should I install it?
>
> Thanks!
>
> "David Wang"
>
> news:1190877162.022203.177650@k79g2000hse.googlegroups.com.. .
>
>
>
> > On Sep 26, 9:11 am, "Jazmin Gutierrez"
> > wrote:
> >> I have a Default Site with port 443 for SSL.
> >> If I have a secondary web site, that uses both 80 and 443 (the same
> >> ports)
> >> but with a different header name, when starting this site I get an err=
or
> >> telling that port 443 is already in use, and that I should assign a
> >> diffent
> >> number.
>
> >> Is is possible to share the 443 port like I share the 80 port?
>
> >> Thanks!
>
> > You can share the SSL port using Host header only if you can use the
> > same SSL Server Certificate for ALL websites that want to share, and
> > you are using IIS6 on Windows Server 2003 SP1 or later.
>
> > This is a restriction of SSL, which does not multiplex endpoints using
> > Host headers because it operates at the TCP, not HTTP (where Host
> > headers exist) layer.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -