Archived from groups: microsoft.public.win2000.dns (
More info?)
Ok, but how do I handle this.
The SSL site is on a different server 10.12.22.6 and the non-ssl Site is on
Server 10.12.22.5
So the problem is I need to resolve it differently depending on port.
Joe
"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
news:OYf4q27eEHA.4092@TK2MSFTNGP10.phx.gbl...
> In news:e3$z9b4eEHA.3200@TK2MSFTNGP09.phx.gbl,
> Joe Coppola <jocojr@hotmail.com> wrote their comments
> Then Kevin replied below:
> > Thanks for the info.
> >
> > Basically, it kinda works like this. my regular port 80
> > site is a test site. However, my 443 site does some live
> > transaction processing.
> >
> > So when someone hits the 443 site they need to be able to
> > access the transaction server, where as everyone else
> > just sees the normal 80 site.
> >
> > I guess another question would be, how do you configure
> > multiple websites on a IIS server (probably not related
> > to this group)
>
> It sorta is related to this group, you can put multiple websites in IIS on
> one IP address, but you can only have one secure site on that same IP
> address. Secure sites will ignore the the host header, but if the name you
> access the secure site by does not match the name of the certificate,
users
> will recieve a warning that the certificate does not match.
> Is all the content in the same virtual website?
> Just mark the directory or page that SSL is required on the page or
> directory, then make all links to the page or directory include https://
> instead of just a relative link, if some one tries to hit the page without
> the https they will get a page that says SSL required. This can be done
all
> in one website on one IP address. Usually though, you would make the
secure
> pages in its own website with a different name and IP address.
>
> But from what I gather there are two different sites, correct?
> It is possible to have the both sites on one IP address, so long as only
one
> is on port 443. You must give the main site without SSL a host header,
such
> a www.example.com (whatever the name you access the site by) but do not
give
> the second site a host header on port 80 and set it to require SSL. That
way
> if someone tries to access by IP without https they only get the SSL
> required page. The SSL site can still be known as www.example.com but it
> must be accessed by
https://www.example.com the SSL certificate must be
> named www.example.com.
>
>
>
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ================================================
> --
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ================================================
> http://www.lonestaramerica.com/
> ================================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ================================================
> Keep a back up of your OE settings and folders
> with OEBackup:
>
http://www.oehelp.com/OEBackup/Default.aspx
> ================================================
>
>