Multiple Host Headers and SSL
Multiple Host Headers and SSL
am 09.05.2006 20:04:49 von Michael Kujawa
Running IIS Version 6.
I have three sites same IP address using host headers.
Each site requires unique SSL Certificate. Each site requires SSL
What can I do?
Can I use different Ports for SSL or am I stuck with each Site
on it's own IP address?
If I can use Different Ports for SSL, what are the ramifications
as far as calling urls from web.
Would I have to use https:/ / mysite.com:4443/ and change all calls for
links?
Or
Will https:/ /mysite.com function as normal?
what would using a different port do to the certificate?
Would it make it invalid?
Re: Multiple Host Headers and SSL
am 09.05.2006 20:17:48 von Michael Kujawa
Found my answer.
Not what I wanted to see
"Michael Kujawa" wrote in message
news:%23WqfRM5cGHA.1436@TK2MSFTNGP05.phx.gbl...
> Running IIS Version 6.
>
> I have three sites same IP address using host headers.
> Each site requires unique SSL Certificate. Each site requires SSL
>
> What can I do?
>
> Can I use different Ports for SSL or am I stuck with each Site
> on it's own IP address?
>
> If I can use Different Ports for SSL, what are the ramifications
> as far as calling urls from web.
>
> Would I have to use https:/ / mysite.com:4443/ and change all calls for
> links?
>
> Or
>
> Will https:/ /mysite.com function as normal?
> what would using a different port do to the certificate?
>
> Would it make it invalid?
>
>
>
Re: Multiple Host Headers and SSL
am 09.05.2006 21:33:45 von IISMVP2005
One option is a wildcard SSL certificate - quite expensive and still limited
to one base domain.
Multiple Port is not a good way to go as some proxy servers will not connect
on a non standard port.
Multiple IP is the only way to go....
--
Cheers
Chris Crowe [IIS MVP 1997 -> 2006]
http://blog.crowe.co.nz
------------------------------------------------
"Michael Kujawa" wrote in message
news:eeY0hT5cGHA.636@TK2MSFTNGP05.phx.gbl...
> Found my answer.
> Not what I wanted to see
>
>
>
>
> "Michael Kujawa" wrote in message
> news:%23WqfRM5cGHA.1436@TK2MSFTNGP05.phx.gbl...
>> Running IIS Version 6.
>>
>> I have three sites same IP address using host headers.
>> Each site requires unique SSL Certificate. Each site requires SSL
>>
>> What can I do?
>>
>> Can I use different Ports for SSL or am I stuck with each Site
>> on it's own IP address?
>>
>> If I can use Different Ports for SSL, what are the ramifications
>> as far as calling urls from web.
>>
>> Would I have to use https:/ / mysite.com:4443/ and change all calls for
>> links?
>>
>> Or
>>
>> Will https:/ /mysite.com function as normal?
>> what would using a different port do to the certificate?
>>
>> Would it make it invalid?
>>
>>
>>
>
>
Re: Multiple Host Headers and SSL
am 09.05.2006 21:59:27 von Michael Kujawa
Yeh,
that is what I found out..
Thanks for the reply
"Chris Crowe [MVP 1997 -> 2006]" wrote in
message news:%23752995cGHA.3556@TK2MSFTNGP02.phx.gbl...
> One option is a wildcard SSL certificate - quite expensive and still
limited
> to one base domain.
>
> Multiple Port is not a good way to go as some proxy servers will not
connect
> on a non standard port.
>
> Multiple IP is the only way to go....
>
>
> --
>
> Cheers
>
> Chris Crowe [IIS MVP 1997 -> 2006]
> http://blog.crowe.co.nz
> ------------------------------------------------
>
>
> "Michael Kujawa" wrote in message
> news:eeY0hT5cGHA.636@TK2MSFTNGP05.phx.gbl...
> > Found my answer.
> > Not what I wanted to see
> >
> >
> >
> >
> > "Michael Kujawa" wrote in message
> > news:%23WqfRM5cGHA.1436@TK2MSFTNGP05.phx.gbl...
> >> Running IIS Version 6.
> >>
> >> I have three sites same IP address using host headers.
> >> Each site requires unique SSL Certificate. Each site requires SSL
> >>
> >> What can I do?
> >>
> >> Can I use different Ports for SSL or am I stuck with each Site
> >> on it's own IP address?
> >>
> >> If I can use Different Ports for SSL, what are the ramifications
> >> as far as calling urls from web.
> >>
> >> Would I have to use https:/ / mysite.com:4443/ and change all calls for
> >> links?
> >>
> >> Or
> >>
> >> Will https:/ /mysite.com function as normal?
> >> what would using a different port do to the certificate?
> >>
> >> Would it make it invalid?
> >>
> >>
> >>
> >
> >
>
>