<p>When Apache starts, it binds to some port and address on

the local machine and waits for incoming requests. By default,

different IP addresses, hostnames and ports.</p>

<p>The <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code>

directive tells the server to accept

address-and-port combinations. If only a port number is

specified in the <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code>

directive, the server

addresses and ports.</p>

<p>For example, to make the server accept connections on both

<div class="example"><p><code>

Listen 80<br />

Listen 8000

</code></p></div>

<div class="example"><p><code>

</code></p></div>

following example:</p>

<div class="example"><p><code>

<p>A growing number of platforms implement IPv6, and

<a class="glossarylink" href="./glossary.html#apr" title="see glossary">APR</a> supports IPv6 on most of these platforms,

<p>One complicating factor for Apache administrators is whether or

not an IPv6 socket can handle both IPv4 connections and IPv6

connections. Handling IPv4 connections with an IPv6 socket uses

IPv4-mapped IPv6 addresses, which are allowed by default on most

special <code class="program"><a href="./programs/configure.html">configure</a></code> parameter can change this behavior

for Apache.</p>

<strong>only</strong> way to handle both IPv6 and IPv4 is to use

mapped addresses. If you want Apache to handle IPv4 and IPv6 connections

with a minimum of sockets, which requires using IPv4-mapped IPv6

addresses, specify the <code>--enable-v4-mapped</code> <code class="program"><a href="./programs/configure.html">configure</a></code> option.</p>

FreeBSD, NetBSD, and OpenBSD, so this is probably how your Apache was

built.</p>

<div class="example"><p><code>

Listen 0.0.0.0:80<br />

</code></p></div>

<p>If your platform supports it and you want Apache to handle IPv4 and

addresses), specify the <code>--disable-v4-mapped</code> <code class="program"><a href="./programs/configure.html">configure</a></code> option. <code>--disable-v4-mapped</code> is the

default on FreeBSD, NetBSD, and OpenBSD.</p>

</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>

<div class="section">

<h2><a name="virtualhost" id="virtualhost">How This Works With Virtual Hosts</a></h2>

<code class="directive"><a href="./mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code>

directives are used, the server will behave

<code class="directive"><a href="./mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code>

can be used to specify a different behavior

VirtualHost, the server must first be told to listen to the

address and port to be used. Then a

<code class="directive"><a href="./mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code> section

behavior of this virtual host. Note that if the

<code class="directive"><a href="./mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code>

is set for an address and port that the

de deux couples d'interfaces et ports, utilisez :</p>

<div class="example"><p><code>

</code></p></div>

<p>Les adresses IPv6 doivent �tre entre crochets, comme dans

<div class="example"><p><code>

Listen 0.0.0.0:80<br />

</code></p></div>

<p>Si votre plateforme le supporte et si vous souhaitez qu'Apache g�re

<a href="./ko/bind.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |

<a href="./tr/bind.html" hreflang="tr" rel="alternate" title="Türkçe">&nbsp;tr&nbsp;</a></p>

</div>

<p>Apache が使用するアドレスとポートの設定をします。</p>

</div>

</p>

<div class="example"><p><code>

</code></p></div>

<p>とします。

<div class="example"><p><code>

Listen 0.0.0.0:80<br />

</code></p></div>

<p>条件を満たすプラットホームで、Apache が

하려면,</p>

<div class="example"><p><code>

</code></p></div>

<p>IPv6 주소는 다음과 같이 대괄호로 묶어야 한다:</p>

<div class="example"><p><code>

Listen 0.0.0.0:80<br />

</code></p></div>

<p>플래폼에서 지원하며 아파치가 서로 다른 소켓으로 IPv4

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">

<?xml-stylesheet type="text/xsl" href="./style/manual.en.xsl"?>

<?xml version="1.0" encoding="iso-2022-jp" ?>

<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">

<?xml-stylesheet type="text/xsl" href="./style/manual.ja.xsl"?>

<?xml version="1.0" encoding="EUC-KR" ?>

<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">

<?xml-stylesheet type="text/xsl" href="./style/manual.ko.xsl"?>

<relpath>.</relpath>

<variants>

<variant>en</variant>

<variant>fr</variant>

<variant outdated="yes">ko</variant>

<variant>tr</variant>

</variants>

to this virtual host (prior to Apache version 1.2 the server

would not even boot).</p>

Then consider this configuration snippet:</p>

<div class="example"><p><code>

ServerAdmin webgirl@abc.dom <br />

DocumentRoot /www/abc <br />

&lt;/VirtualHost&gt;

<p>Here is a snippet that avoids both of these problems:</p>

<div class="example"><p><code>

ServerName www.abc.dom <br />

ServerAdmin webgirl@abc.dom <br />

DocumentRoot /www/abc <br />

&lt;/VirtualHost&gt;

</code></p></div>

<code>www.def.dom</code>. Furthermore, suppose that

<code>def.dom</code> has control of their own DNS. With this

config you have put <code>def.dom</code> into a position where

they can steal all traffic destined to <code>abc.dom</code>. To

do so, all they have to do is set <code>www.def.dom</code> to

from pointing the <code>www.def.dom</code> record wherever they

wish.</p>

users typed in URLs of the form

<code>http://www.abc.dom/whatever</code>) will all be served by

the <code>def.dom</code> virtual host. To better understand why