address comment http://httpd.apache.org/docs/2.4/vhosts/examples.html#comment_1441 by

explicitly mentioning that ServerName may be calculated and inherited.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1500042 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/vhosts/name-based.xml b/docs/manual/vhosts/name-based.xml
index 9fbf2ad44e7183873b49194c4869b8537f47d114..c35c2b9ce1c0cf382851eef3d080611d51afe832 100644 (file)
--- a/docs/manual/vhosts/name-based.xml
+++ b/docs/manual/vhosts/name-based.xml
@@ -122,6 +122,19 @@
         virtual hosts.</p>
     </note>
 
+    <note><title>ServerName inheritance</title>
+       <p> It is best to always explicitly list a  <directive module="core"
+       >ServerName</directive> in every name-based virtual host.</p>
+       <p>If a <directive module="core">VirtualHost</directive> doesn't specify 
+       a <directive module="core">ServerName</directive>, a server name will be 
+       inherited from the base server configuration.  If no server name was 
+       specified globally, one is detected at startup through reverse DNS resolution
+       of the first listening address.  In either case, this inherited server name
+       will influenced name-based virtual host resolution, so it is best to always
+       explicitly list a  <directive module="core">ServerName</directive> in every
+       name-based virtual host.</p>
+    </note>
+
     <p>For example, suppose that you are serving the domain
     <code>www.example.com</code> and you wish to add the virtual host
     <code>other.example.com</code>, which points at the same IP address.