After biting the bullet on my inability to use a single IP for multiple SSL
hosts (and using up a couple of extra IP's), I am left wondering something.
Why doesn't IP/port based virtual hosting (say, 1.2.3.4:443, 1.2.3.4:11001,
1.2.3.4:11002, 1.2.3.4:11003, etc) work. Assuming you explicitly tell the
client the port number with every link, what breaks SSL with this type of
virtual host?
I tried many different ways of getting this to work, but had no luck. Mads,
maybe you could shed some light.
-----Original Message-----
From: Mads Toftum [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 07, 2000 3:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Another Virtual Hosts Question (1 SSL + 2 non-SSL, all
virtual)
On Sun, Aug 06, 2000 at 07:17:24PM -0500, James Moore wrote:
>
> Q: will name-based virtual hosting support this, or do I need to use an
> IP-based virtual host for the https?
>
IP-based. See http://www.modssl.org/docs/2.6/ssl_faq.html#vhosts
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
