It was thus said that the Great Chris me once stated:
> I set up each entry with <VirtualHost *:443> but when I do that, the
> second site will complain that the cert is for site1. So if I go to
> site2.com, I get a browser error that the cert is for site1. It will show
> me the content for site1.
On my development server, I have the following:
<VirtualHost 192.168.1.10:443>
ServerName playground.roswell.area51
SSLEngine on
SSLCertificateFile /home/spc/web/playground/cert.pem
SSLCertificateKeyFile /home/spc/web/playground/key.pem
...
</virtualHost>
<virtualHost 1932.168.1.10:443>
ServerName wiki.roswell.area51
SSLEngine on
SSLCertificateFile /home/spc/web/wiki/cert.pem
SSLCertificateKeyFile /home/spc/web/wiki/key.pem
...
</VirtualHost>
> I am not sure how to do this part:
> Do not use the 2.2 authz directives (Allow/Deny/Order) and use Require instead
> I am running Apache 2.2, does it still apply?
> It does not look like mod_access_compat is listed under mods-enabled
That I don't remember as I've been running Apache 2.4 for a couple of
years now.
-spc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
