Birmingham mumbai

                ErrorLog ${APACHE_LOG_DIR}/acmeconsulting.com-error.log 
                CustomLog ${APACHE_LOG_DIR}/acmeconsulting.com-access. 
                log combined 
 
                SSLEngine on 

---

Chapter 14
[
 365 
]
        SSLCertificateFile      /etc/apache2/certs/acmeconsulting/acme. 
        crt 
        SSLCertificateKeyFile /etc/apache2/certs/acmeconsulting/acme. 
        key 
 
                 
                                SSLOptions +StdEnvVars 
                 
                 
                                SSLOptions +StdEnvVars 
                 
 
         
 
Basically, what I did was create a new virtual host configuration file (using the 
existing 
default-ssl.conf
 file as a template). I called this new file 
acme-consulting.
conf
 and I stored it in the 
/etc/apache2/sites-available
 directory. I changed the 
VirtualHost
 line to listen for anything coming in on port 
443
. The line 
ServerName 
acmeconsulting.com:443
 was added to make this file responsible for traffic coming 
in looking for 
acmeconsulting.com
 on port 
443
. I also set 
DocumentRoot
 to 
/var/www/
acmeconsulting
. In addition, I customized the error and access logs so that it will be 
easier to find log messages relating to this new site, since its log entries will go to 
their own specific files.
In my experience, I find that a modular approach, such as what I've done with the 
sample virtual host file for HTTPS, works best when setting up a web server that's 
intended to host multiple websites. With each site, I'll typically give it its own 
document root, certificate files, and log files. Even if you're only planning on hosting 
a single site on your server, using this modular approach is still a good idea, since 
you may want to host additional sites later on.
So, there you have it. You should now understand how to set up secure virtual hosts 
in Apache. However, security doesn't equal redundancy.