Re: SSL on IIS6.0 Multi-Homed
From: Bernard (qbernard_at_hotmail.com.discuss)
Date: 03/26/04
- Next message: Jerry Pisk: "Re: Multiple Site"
- Previous message: Steven Burn: "Re: SERIOUS VIOLATION OF MY PRIVACY ?????"
- In reply to: CQL User: "SSL on IIS6.0 Multi-Homed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 26 Mar 2004 14:59:16 +0800
1) if you configure 2 host header in the secure site.
when you type https://www.multi.com, you should be prompt
to validate the cert as the common name does't match with the cert.
2) I'm not sure why you get redirected.. you might want to check
if you have configure custom error page to redirect to https://secure....
3) and SSL doesn't support host header.
-- Regards, Bernard Cheah http://support.microsoft.com/ http://www.msmvps.com/bernard/ "CQL User" <foo@cqlcorp.com> wrote in message news:uknOZcnEEHA.2408@TK2MSFTNGP10.phx.gbl... > I am having a problem on Windows 2003 Server. > > On 2000, I could have a multi-homed server, as long as I only had 1 SSL per > IP. ie: port 443. > > If the certificate was assigned to https://secure.foo.com, it works fine. > > If I go to a multi-homed site, on the same IP, but NO SSL included, and I > typed in the multi-homed SSL, ie: https://www.multi.com, I should get an > error. However, it actually redirects to https://secure.foo.com and allows > the lock to appear and work. (even though the SSL is assigned to > https://secure.foo.com.) > > Is this a bug? Should I be able to do this? I followed the instructions. > Shouldn't the SSL still look at the host header, to realize I am not going > to the valid address? > > Please advise! > >
- Next message: Jerry Pisk: "Re: Multiple Site"
- Previous message: Steven Burn: "Re: SERIOUS VIOLATION OF MY PRIVACY ?????"
- In reply to: CQL User: "SSL on IIS6.0 Multi-Homed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|