Hi Aaron,
As I uderstand, the docks say you can't have name based virtual hosts
because SSL is alreday serving the page before apache sees any http
header?
In the example I posted, https://mail.mydomain.net works and takes me
to my webmail, and https://machinename.mydomain.net works and takes
me
Glyn Astill wrote:
Hi Aaron,
As I uderstand, the docks say you can't have name based virtual hosts
because SSL is alreday serving the page before apache sees any http
header?
That is essentially correct.
In the example I posted, https://mail.mydomain.net works and takes me
to my
Glyn Astill wrote:
Hi people,
So I got ssl started, and now I'm trying to sort out my virtual hosts
but I can't seem to get them to work.
Due to the fundamental nature of SSL and virtual host resolution one may
not have more than one SSL-enabled virtual host per IP:port combination.
On Fri, Feb 20, 2004 at 11:18:10AM +0100, Svein E. Seldal wrote:
I'm running Debian testing latest versions on a i686:
Server Version: Apache/1.3.29 Ben-SSL/1.52 (Debian GNU/Linux)
debian versions: apache-ssl 1.3.29.0.1-5
You're asking on the wrong list then - this is the mod_ssl list, while
-Original Message-
From: Mads Toftum [mailto:[EMAIL PROTECTED]
Server Version: Apache/1.3.29 Ben-SSL/1.52 (Debian GNU/Linux)
debian versions: apache-ssl 1.3.29.0.1-5
You're asking on the wrong list then - this is the mod_ssl list, while
you're running apache-ssl which lives at