summaryrefslogtreecommitdiffstats
path: root/docs/manual/vhosts/name-based.html.en
diff options
context:
space:
mode:
authorDaniel Earl Poirier <poirier@apache.org>2010-08-19 20:05:20 +0200
committerDaniel Earl Poirier <poirier@apache.org>2010-08-19 20:05:20 +0200
commit8f2f7c1807153d748eaf71031512d41401df1734 (patch)
tree0b7d6272f13e7add701630deeb6b6957dd622b52 /docs/manual/vhosts/name-based.html.en
parentOverhaul the detailed doc for virtual hosts: (diff)
downloadapache2-8f2f7c1807153d748eaf71031512d41401df1734.tar.xz
apache2-8f2f7c1807153d748eaf71031512d41401df1734.zip
Update transforms and add some html and meta files generated from new pages
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@987255 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/vhosts/name-based.html.en')
-rw-r--r--docs/manual/vhosts/name-based.html.en20
1 files changed, 13 insertions, 7 deletions
diff --git a/docs/manual/vhosts/name-based.html.en b/docs/manual/vhosts/name-based.html.en
index 6a33bad273..cba1b63ec9 100644
--- a/docs/manual/vhosts/name-based.html.en
+++ b/docs/manual/vhosts/name-based.html.en
@@ -35,9 +35,11 @@
<div class="section">
<h2><a name="namevip" id="namevip">Name-based vs. IP-based Virtual Hosts</a></h2>
- <p>IP-based virtual hosts use the IP address of the connection to
+ <p><a href="ip-based.html">IP-based virtual hosts</a> use the IP address of the connection to
determine the correct virtual host to serve. Therefore you need to
- have a separate IP address for each host. With name-based virtual
+ have a separate IP address for each host.</p>
+
+ <p>With name-based virtual
hosting, the server relies on the client to report the hostname as
part of the HTTP headers. Using this technique, many different hosts
can share the same IP address.</p>
@@ -52,7 +54,8 @@
using IP-based virtual hosting:</p>
<ul>
- <li>Name-based virtual hosting cannot be used with SSL secure servers
+ <li>Name-based virtual hosting often <a href="../ssl/ssl_faq.html#vhosts">
+ cannot be used with SSL secure servers</a>
because of the nature of the SSL protocol.</li>
<li>Some operating systems and network equipment implement bandwidth
@@ -68,16 +71,19 @@
<p>To use name-based virtual hosting, you must designate the IP
address (and possibly port) on the server that will be accepting
- requests for the hosts. This is configured using the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive.
+ requests that need to be distinguished by hostname.
+ This is configured using the <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive.
In the normal case where any and all IP addresses on the server should
be used, you can use <code>*</code> as the argument to <code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code>. If you're planning to use
multiple ports (e.g. running SSL) you should add a Port to the argument,
- such as <code>*:80</code>. Note that mentioning an IP address in a
+ such as <code>*:80</code>.</p>
+
+ <div class="note"><p>Note that mentioning an IP address in a
<code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive does not
- automatically make the server listen to that IP address. See
+ automatically make the server <em>listen</em> to that IP address. See
<a href="../bind.html">Setting which addresses and ports Apache uses</a>
for more details. In addition, any IP address specified here must be
- associated with a network interface on the server.</p>
+ associated with a network interface on the server.</p></div>
<p>The next step is to create a <code class="directive"><a href="../mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code> block for
each different host that you would like to serve. The argument to the