[EMAIL PROTECTED] wrote: > > Martin > Is the domain your typing https:// to a virtual domain without unique ip > address? > As far as I know if your using virtual domains they have to have each their > own unique ip address to get your https to serve up a web page. > I have been told that your server does not un-encrypt the session to find > the virtual domain and then setup and a secure session with that domain. > But instead it must connect directly to that domain via ip address. So If > you have a virtual table like me. And all your domains are currently using > the same IP address. You will get the result that you described. Just to be clear, it is true that the server does not get the server-name in a https request which is the reason you cannot have name-based virtual hosts under SSL. However, remember that HTTP is on port 80 and HTTPS is on port 443 so you can have many HTTP virtual hosts and exactly one HTTPS host on the *same* IP address. >> Martin: Your problem is that you need to define a virtual host for HTTPS/SSL. The minimal config is: Listen 443 <VirtualHost 192.168.1.1:443> SSLEngine on SSLCertificateFile /home/apache/conf/ssl.crt/your_site.crt SSLCertificateKeyFile /home/apache/conf/ssl.key/your_site.key DocumentRoot /home/apache/html/ssl_content </VirtualHost> Rgds, Owen Boyle. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
