On Wed, 2004-03-24 at 08:01, Russell Coker wrote: > On Wed, 24 Mar 2004 22:22, Michael Stone <[EMAIL PROTECTED]> wrote: > > The best you could do would be to attach different certificates to > > different ports, but that would be extremely cumbersome and probably > > would lead to confusion. > > What if you had http://www.company1.com/ redirect to > https://www.company1.com:81/ and http://www.company2.com/ redirect to > https://www.company2.com:82/ ? > > www.company1.com and www.company2.com would have the same IP address. This > should work.
Why go that route. Many Proxies do not allow :81 :82 etc... It would suck. How many instances would that force you to run anyway. Many. Almost be easier to just say SSL == Separate virtual/real machine, and that would suck as well. But, on the flip-side, most companies/people wanting SSL typically want their own machine to keep the info "safe" from other prying eyes. -- [EMAIL PROTECTED] REMEMBER ED CURRY! http://www.iwethey.org/ed_curry Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup
signature.asc
Description: This is a digitally signed message part
