You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2014/10/01 14:40:59 UTC
svn commit: r1628690 - /httpd/httpd/trunk/docs/manual/vhosts/examples.xml
Author: covener
Date: Wed Oct 1 12:40:58 2014
New Revision: 1628690
URL: http://svn.apache.org/r1628690
Log:
reword/reorg/simplify based on recent feedback.
- don't worry about how multiple IP addresses map
- simplify the description of why you might use an IP address in <virtualhost
- move the note below the last paragraph
Modified:
httpd/httpd/trunk/docs/manual/vhosts/examples.xml
Modified: httpd/httpd/trunk/docs/manual/vhosts/examples.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/vhosts/examples.xml?rev=1628690&r1=1628689&r2=1628690&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/vhosts/examples.xml (original)
+++ httpd/httpd/trunk/docs/manual/vhosts/examples.xml Wed Oct 1 12:40:58 2014
@@ -38,10 +38,9 @@
<section id="purename"><title>Running several name-based web
sites on a single IP address.</title>
- <p>Your server has a single IP address, and multiple aliases (CNAMES)
- point to this machine in DNS. You want to run a web server for
- <code>www.example.com</code> and <code>www.example.org</code> on this
- machine.</p>
+ <p>Your server has multiple hostnames that resolve to a single address,
+ and you want to respond differently for <code>www.example.com</code>
+ and <code>www.example.org</code>.</p>
<note><title>Note</title><p>Creating virtual
host configurations on your Apache server does not magically
@@ -80,12 +79,18 @@ Listen 80
<code>ServerName</code> directives, it will be served by this first
<code>VirtualHost</code>.</p>
+ <p>The above configuration is what you will want to use in almost
+ all name-based virtual hosting situations. The only thing that this
+ configuration will not work for, in fact, is when you are serving
+ different content based on differing IP addresses or ports.</p>
+
<note>
<title>Note</title>
- <p>You can, if you wish, replace <code>*</code> with the actual
- IP address of the system, when you don't care to discriminate based
- on the IP address or port.</p>
+ <p>You may replace <code>*</code> with a specific IP address
+ on the system. Such virtual hosts will only be used for
+ HTTP requests received on connection to the specified IP
+ address.</p>
<p>However, it is additionally useful to use <code>*</code>
on systems where the IP address is not predictable - for
@@ -95,12 +100,6 @@ Listen 80
would work without changes whenever your IP address
changes.</p>
</note>
-
- <p>The above configuration is what you will want to use in almost
- all name-based virtual hosting situations. The only thing that this
- configuration will not work for, in fact, is when you are serving
- different content based on differing IP addresses or ports.</p>
-
</section>
<section id="twoips"><title>Name-based hosts on more than one