summaryrefslogtreecommitdiff
path: root/docs/manual/vhosts/ip-based.html.en
diff options
context:
space:
mode:
Diffstat (limited to 'docs/manual/vhosts/ip-based.html.en')
-rw-r--r--docs/manual/vhosts/ip-based.html.en10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/manual/vhosts/ip-based.html.en b/docs/manual/vhosts/ip-based.html.en
index c3c3b71ce2..72eed1fde4 100644
--- a/docs/manual/vhosts/ip-based.html.en
+++ b/docs/manual/vhosts/ip-based.html.en
@@ -41,7 +41,7 @@
</li><li><a href="#comments_section">Comments</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="explanation" id="explanation">What is IP-based virtual hosting</a></h2>
+<h2><a name="explanation" id="explanation">What is IP-based virtual hosting</a><a title="Permanent link" href="#explanation" class="permalink">&para;</a></h2>
<p>IP-based virtual hosting is a method to apply different directives
based on the IP address and port a request is received on. Most commonly,
this is used to serve different websites on different ports or interfaces.</p>
@@ -53,7 +53,7 @@ See <a href="name-based.html#namevip">Name-based vs. IP-based
Virtual Hosts</a> to help you decide. </p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="requirements" id="requirements">System requirements</a></h2>
+<h2><a name="requirements" id="requirements">System requirements</a><a title="Permanent link" href="#requirements" class="permalink">&para;</a></h2>
<p>As the term <cite>IP-based</cite> indicates, the server
<strong>must have a different IP address/port combination for each IP-based
@@ -70,7 +70,7 @@ Virtual Hosts</a> to help you decide. </p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="howto" id="howto">How to set up Apache</a></h2>
+<h2><a name="howto" id="howto">How to set up Apache</a><a title="Permanent link" href="#howto" class="permalink">&para;</a></h2>
<p>There are two ways of configuring apache to support multiple
hosts. Either by running a separate <code class="program"><a href="../programs/httpd.html">httpd</a></code> daemon for
@@ -108,7 +108,7 @@ Virtual Hosts</a> to help you decide. </p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="multiple" id="multiple">Setting up multiple daemons</a></h2>
+<h2><a name="multiple" id="multiple">Setting up multiple daemons</a><a title="Permanent link" href="#multiple" class="permalink">&para;</a></h2>
<p>Create a separate <code class="program"><a href="../programs/httpd.html">httpd</a></code> installation for each
virtual host. For each installation, use the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the
@@ -124,7 +124,7 @@ Virtual Hosts</a> to help you decide. </p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="single" id="single">Setting up a single daemon
- with virtual hosts</a></h2>
+ with virtual hosts</a><a title="Permanent link" href="#single" class="permalink">&para;</a></h2>
<p>For this case, a single <code class="program"><a href="../programs/httpd.html">httpd</a></code> will service
requests for the main server and all the virtual hosts. The <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> directive