Re: Multiple website in single IP, host header and SSL problem

This only works if you have a wildcard SSL certification (*.domain.com) and
all your hosts belong to the same domain. It does not work if you have
domain1.com and domain2.com

Cheers
Ken

"prof_martin" <profmartin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:032D45ED-30BA-475B-9E43-DFD131B680CF@xxxxxxxxxxxxxxxx
Hi Ken, Thanks for the reply,

Now I understand how it can be like that. Anyway Bernard Cheah already
told
me that Win2003 SP1 can solve the issue of having SSL if using host
header.
I'll try to work on it.

Thanks I appreciate that.
Martin Adhie

"Ken Schaefer" wrote:

There is nothing wrong with your configuration. Because there is only one
SSL-enabled website, any SSL requests will go through to that website.
Host-Headers can not be used with SSL, because the Host header sent from
the
browser is encrypted so IIS can't use it to route requests to websites:
only
IP addresses and port numbers can be used.

Cheers
Ken

"prof_martin" <profmartin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F7CE0384-E8FE-491E-922F-E73CFEA7E369@xxxxxxxxxxxxxxxx
Hi,

I have websites hosted in one server, single IP address using host
header
in
IIS 6.0 (windows 2003 standard ed.)
For illustration, in IIS I created 4 websites for respective domain
name
indentified on host header:

www.domain1.com
domain1.com
www.domain2.com
domain2.com

I installed SSL on website www.domain1.com
If I type https://www.domain1.com works fine.
If I type https://domain1.com should be OK, although promp security for
different site name

Problem is, if I type https://www.domain2.com or https://domain2.com,
it
prompt security message and display www.domain1.com content.

Should be something wrong in my configuration.

I very appreciate for any person who can help solve this problem.

Thank you,
Martin Adhie






.

Relevant Pages

  • 85010014 error - Exchange ActiveSync - Resolved
    ... Application Log on our server would be filled with those ActiveSync 3005: ... It basically all comes down to the basics of Windows DNS, how SSL ... and our Default Website could only properly respond to ONE IP ... SSL host header using port 443 with our SSL cert. ...
    (microsoft.public.exchange.connectivity)
  • 85010014 error - resolved - ActiveSync Exchange Server
    ... Application Log on our server would be filled with those ActiveSync 3005: ... It basically all comes down to the basics of Windows DNS, how SSL ... and our Default Website could only properly respond to ONE IP ... SSL host header using port 443 with our SSL cert. ...
    (microsoft.public.pocketpc.activesync)
  • Re: 85010014 error - resolved - ActiveSync Exchange Server
    ... Application Log on our server would be filled with those ActiveSync 3005: ... It basically all comes down to the basics of Windows DNS, how SSL ... and our Default Website could only properly respond to ONE IP ... SSL host header using port 443 with our SSL cert. ...
    (microsoft.public.pocketpc.activesync)
  • Re: Multiple Sites running same code, w/SSL.
    ... This is a limitation in SSL, not IIS. ... Here is the problem -- Host header is a property of the HTTP request (it is ... the website and hence server certificate, is encrypted in the very thing ...
    (microsoft.public.inetserver.iis.security)
  • Re: How to host muliple web sites in IIS6.0 all must be SSl
    ... You can not use host-headers with SSL - this is because the Host: ... each SSL secured website must run on its own IP ... The server ...
    (microsoft.public.inetserver.iis)