Actually to clarify point 3. That error I stated was due to something else.
However I tested the following config and the first virtualhost completely
over-rides the second one due to the wildcard.
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /var/www/html/centos
ServerName centos.local
ServerAlias centos2.local centos3.local
#ServerAlias centos4.local *.local
ServerAlias centos5.local
ErrorLog logs/centos-error_log
CustomLog logs/centos-access_log common
<Directory "/var/www/html/centos">
allow from all
Options +Indexes
</Directory>
</VirtualHost>
#
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /var/www/html/centos2
ServerName centos20.local
ErrorLog logs/centos2-error_log
CustomLog logs/centos2-access_log common
<Directory "/var/www/html/centos2">
allow from all
Options +Indexes
</Directory>
</VirtualHost>
From: Rose, John B <[email protected]> <[email protected]>
Reply: [email protected] <[email protected]>
<[email protected]>
Date: 16 March 2017 at 11:31:17 PM
To: [email protected] <[email protected]> <[email protected]>
Subject: [users@httpd] ServerAlias limit and conflicts?
1. Is there a limit on how many “ServerAlias” lines can be in a
virtual host block?
2. Is there a limit on how many hostnames can be in one “ServerAlias”
line?
3. If you used “ServerAlias *.abc.com” in one virtual host conf file,
would that cause any conflict with existing virtual host conf files using
the same abc.com domain?
Thanks
