Speaking about virtualhosts, we had the same problem for a project of ours. The Apache's "ServerName" directive isn't optional, it's mandatory to use. Apache has no such thing as a "default" virtualhost to load when it has no ServerName match. IfAnd if virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost. This is he got a bit of an "empiric" discovery anywayconfiguration loaded for that address. The correct way to do it all is to have virtualhosts detailing all of the possible servernames in ServerName and ServerAlias directive. See name based virtual hosting on apache, and readconsider carefully the evidenced note "Main host goes away".
Speaking about virtualhosts, we had the same problem for a project of ours. Apache has no such thing as a "default" virtualhost. If virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost. This is a bit of an "empiric" discovery anyway. The correct way to do it all is to have virtualhosts detailing all of the possible servernames. See name based virtual hosting on apache, and read carefully the evidenced note "Main host goes away".
Speaking about virtualhosts, we had the same problem for a project of ours. The Apache's "ServerName" directive isn't optional, it's mandatory to use. Apache has no such thing as a "default" virtualhost to load when it has no ServerName match. And if virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost he got a configuration loaded for that address. The correct way to do it all is to have virtualhosts detailing all of the possible servernames in ServerName and ServerAlias directive. See name based virtual hosting on apache, and consider carefully the evidenced note "Main host goes away".
Speaking about virtualhosts, we had the same problem for a project of ours. Apache has no such thing as a "default" virtualhost. If virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost. This is a bit of an "empiric" discovery anyway. The correct way to do it all is to have virtualhosts detailing all of the possible servernames. See name based virtual hosting on apache, and read carefully the evidenced note "Main host goes away".
Speaking about virtualhosts, we had the same problem for a project of ours. Apache has no such thing as a "default" virtualhost. If virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost.
Speaking about virtualhosts, we had the same problem for a project of ours. Apache has no such thing as a "default" virtualhost. If virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost. This is a bit of an "empiric" discovery anyway. The correct way to do it all is to have virtualhosts detailing all of the possible servernames. See name based virtual hosting on apache, and read carefully the evidenced note "Main host goes away".
Speaking about virtualhosts, we had the same problem for a project of ours. Apache has no such thing as a "default" virtualhost. If virtualhost servernames overlap, well, that's just going to give you problems. In the end in those cases Apache just decides what to do depending on its configuration files loading order. And if you try to contact the server through an unspecified address (ip address, or something not mapped on the virtualhost) it will load the first virtualhost.