Subject: RE: Virtual Hosting Problem

From: "Boyle Owen" <[email-masked]>
Date: Mon, 29 Jul 2002 09:03:22 +0200

>From: Danalien [mailto:[email-masked]]
>
>As I know, you can only bind one uniqe ip to one SSL virtual host.

not quite - see below..

>and from what I have read, you can't use name-based SSL 
>virtual host(s) either,
>as a work around.

Mostly right, but with one privisio: You cannot do name-based VHs with SSL but you can have many SSL port-based VHs on ONE IP address..

To understand why - Because in SSL the contents of the TCP/IP packets are encrypted, you can only use external TCP/IP attributes (i.e. IP address and port number) to route the packets. For name-based VHing, you need access to the Host header which is an HTTP attribute (i.e. it is inside the TCP/IP packet). This is visible in plain HTTP but not visible in SSL.

>
>>(48)Address already in use: make_sock: could not bind to 
>address [::]:447
>>no listening sockets available, shutting down

This usually means that some other process is already using port 447. Check /etc/services for a list of pre-defined ports, also verify that you have completely killed all other instances of apache which may have been blocking the port (ps -ef ¦ grep httpd).

Rgds,

Owen Boyle
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [email-masked]
Automated List Manager                            [email-masked]