Gecko [ v3.cesa.co.za ]

Name	Size	Permission	Date
details.html	19.89 KB	-rw-r--r--	2026-06-12 05:08
examples.html	24.51 KB	-rw-r--r--	2026-06-12 05:08
fd-limits.html	8.78 KB	-rw-r--r--	2026-06-12 05:08
index.html	9.98 KB	-rw-r--r--	2026-06-12 05:08
ip-based.html	13.26 KB	-rw-r--r--	2026-06-12 05:08
mass.html	18.38 KB	-rw-r--r--	2026-06-12 05:08
name-based.html	21.34 KB	-rw-r--r--	2026-06-12 05:08

Rename

<!DOCTYPE html SYSTEM "about:legacy-compat">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta content="width=device-width, initial-scale=1" name="viewport">

<title>Apache IP-based Virtual Host Support - Apache HTTP Server Version 2.4</title>
<link href="../../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet">
<link href="../../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size">
<link href="../../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css"><link rel="stylesheet" type="text/css" href="../../style/css/prettify.css">
<script src="../../style/scripts/prettify.min.js">
</script>

<p>In many cases, <a href="name-based.html">name-based
virtual hosts</a> are more convenient, because they allow
many virtual hosts to share a single address/port.
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 id="requirements">System requirements <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
    virtual host</strong>. This can be achieved by the machine
    having several physical network connections, or by use of
    virtual interfaces which are supported by most modern operating
    systems (see system documentation for details, these are
    frequently called "ip aliases", and the "ifconfig" command is
    most commonly used to set them up), and/or using multiple
    port numbers.</p>

<p> In the terminology of Apache HTTP Server, using a single IP address
    but multiple TCP ports, is also IP-based virtual hosting.</p>

</div><div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="section">
<h2 id="howto">How to set up Apache <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
    each hostname, or by running a single daemon which supports all the
    virtual hosts.</p>

<p>Use multiple daemons when:</p>

<ul>
      <li>There are security partitioning issues, such as company1
      does not want anyone at company2 to be able to read their
      data except via the web. In this case you would need two
      daemons, each running with different <code class="directive"><a href="../mod/mod_unixd.html#user">User</a></code>, <code class="directive"><a href="../mod/mod_unixd.html#group">Group</a></code>, <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, and <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> settings.</li>

<li>You can afford the memory and file descriptor
      requirements of listening to every IP alias on the
      machine. It's only possible to <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> to the "wildcard"
      address, or to specific addresses. So if you have a need to
      listen to a specific address for whatever reason, then you
      will need to listen to all specific addresses. (Although one
      <code class="program"><a href="../programs/httpd.html">httpd</a></code> could listen to N-1 of the addresses, and another could
      listen to the remaining address.)</li>
    </ul>

<p>Use a single daemon when:</p>

<ul>
      <li>Sharing of the httpd configuration between virtual hosts
      is acceptable.</li>

<li>The machine services a large number of requests, and so
      the performance loss in running separate daemons may be
      significant.</li>
    </ul>

</div><div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="section">
<h2 id="multiple">Setting up multiple daemons <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
    configuration file to select which IP address (or virtual host)
    that daemon services. e.g.</p>

<pre class="prettyprint lang-config">Listen 192.0.2.100:80</pre>

<p>It is recommended that you use an IP address instead of a
    hostname (see <a href="../dns-caveats.html">DNS caveats</a>).</p>

</div><div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="section">
<h2 id="single">Setting up a single daemon
  with virtual hosts <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
    in the configuration file is used to set the values of <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code>, <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>, <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code> and <code class="directive"><a href="../mod/mod_log_config.html#transferlog">TransferLog</a></code>
    or <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code>
    configuration directives to different values for each virtual
    host. e.g.</p>

<pre class="prettyprint lang-config">&lt;VirtualHost 172.20.30.40:80&gt;
    ServerAdmin webmaster@www1.example.com
    DocumentRoot "/www/vhosts/www1"
    ServerName www1.example.com
    ErrorLog "/www/logs/www1/error_log"
    CustomLog "/www/logs/www1/access_log" combined
&lt;/VirtualHost&gt;

&lt;VirtualHost 172.20.30.50:80&gt;
    ServerAdmin webmaster@www2.example.org
    DocumentRoot "/www/vhosts/www2"
    ServerName www2.example.org
    ErrorLog "/www/logs/www2/error_log"
    CustomLog "/www/logs/www2/access_log" combined
&lt;/VirtualHost&gt;</pre>

<p>It is recommended that you use an IP address instead of a
    hostname in the &lt;VirtualHost&gt; directive
    (see <a href="../dns-caveats.html">DNS caveats</a>).</p>

<p> Specific IP addresses or ports have precedence over their wildcard
    equivalents, and any virtual host that matches has precedence over
    the servers base configuration.</p>

<p>Almost <strong>any</strong> configuration directive can be
    put in the VirtualHost directive, with the exception of
    directives that control process creation and a few other
    directives. To find out if a directive can be used in the
    VirtualHost directive, check the <a href="../mod/directive-dict.html#Context">Context</a> using the
    <a href="../mod/quickreference.html">directive index</a>.</p>

<p><code class="directive"><a href="../mod/mod_suexec.html#suexecusergroup">SuexecUserGroup</a></code>
    may be used inside a
    VirtualHost directive if the <a href="../suexec.html">suEXEC
    wrapper</a> is used.</p>

<p><em>SECURITY:</em> When specifying where to write log files,
    be aware of some security risks which are present if anyone
    other than the user that starts Apache has write access to the
    directory where they are written. See the <a href="../misc/security_tips.html">security tips</a> document
    for details.</p>

</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../../en/vhosts/ip-based.html" title="English">&nbsp;en&nbsp;</a> |
<a href="../../fr/vhosts/ip-based.html" hreflang="fr" rel="alternate" title="Fran&ccedil;ais">&nbsp;fr&nbsp;</a> |
<a href="../../ja/vhosts/ip-based.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
<a href="../../ko/vhosts/ip-based.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
<a href="../../tr/vhosts/ip-based.html" hreflang="tr" rel="alternate" title="T&uuml;rk&ccedil;e">&nbsp;tr&nbsp;</a></p>
</div><div id="footer">
<p class="apache">Copyright 2026 The Apache Software Foundation.<br>Licensed under the <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="../mod/index.html">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="https://cwiki.apache.org/confluence/display/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a> | <a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2">Report a bug</a></p></div><script><![CDATA[//><!]]></script>
</body></html>