bind.html.en revision 330d21e087f40d0b296ae96d6de57c27cba83b99
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<?xml version="1.0" encoding="ISO-8859-1"?>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd This file is generated from xml source: DO NOT EDIT
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd -->
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<title>Binding to Addresses and Ports - Apache HTTP Server</title>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<link href="/style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<link href="/images/favicon.ico" rel="shortcut icon" /></head>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<body id="manual-page"><div id="page-header">
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<p class="apache">Apache HTTP Server Version 2.3</p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<img alt="" src="/images/feather.gif" /></div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="/images/left.gif" /></a></div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<div id="path">
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="./">Version 2.3</a></div><div id="page-content"><div id="preamble"><h1>Binding to Addresses and Ports</h1>
3b3b7fc78d1f5bfc2769903375050048ff41ff26nd<div class="toplang">
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<p><span>Available Languages: </span><a href="/de/bind.html" hreflang="de" rel="alternate" title="Deutsch">&nbsp;de&nbsp;</a> |
3b3b7fc78d1f5bfc2769903375050048ff41ff26nd<a href="/en/bind.html" title="English">&nbsp;en&nbsp;</a> |
3b3b7fc78d1f5bfc2769903375050048ff41ff26nd<a href="/fr/bind.html" hreflang="fr" rel="alternate" title="Fran�ais">&nbsp;fr&nbsp;</a> |
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<a href="/ja/bind.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<a href="/ko/bind.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<a href="/tr/bind.html" hreflang="tr" rel="alternate" title="T�rk�e">&nbsp;tr&nbsp;</a></p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd</div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <p>Configuring Apache HTTP Server to listen on specific addresses and ports.</p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd </div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#overview">Overview</a></li>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<li><img alt="" src="/images/down.gif" /> <a href="#ipv6">Special IPv6 Considerations</a></li>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<li><img alt="" src="/images/down.gif" /> <a href="#protocol">Specifying the protocol with Listen</a></li>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<li><img alt="" src="/images/down.gif" /> <a href="#virtualhost">How This Works With Virtual Hosts</a></li>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd</ul><h3>See also</h3><ul class="seealso"><li><a href="vhosts/">Virtual Hosts</a></li><li><a href="dns-caveats.html">DNS Issues</a></li></ul></div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<div class="section">
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd<h2><a name="overview" id="overview">Overview</a></h2>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="/mod/core.html">core</a></code></li><li><code class="module"><a href="/mod/mpm_common.html">mpm_common</a></code></li></ul></td><td><ul><li><code class="directive"><a href="/mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code></li><li><code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code></li></ul></td></tr></table>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <p>When httpd starts, it binds to some port and address on
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd the local machine and waits for incoming requests. By default,
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd it listens to all addresses on the machine. However, it may need to
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd be told to listen on specific ports, or only on selected
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd addresses, or a combination of both. This is often combined with the
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <a href="vhosts.html">Virtual Host</a> feature, which determines how
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <code>httpd</code> responds to different IP addresses, hostnames and
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd ports.</p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <p>The <code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd directive tells the server to accept
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd incoming requests only on the specified port(s) or
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd address-and-port combinations. If only a port number is
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd specified in the <code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd directive, the server listens to the given port on all interfaces.
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd If an IP address is given as well as a port, the server will listen
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd on the given port and interface. Multiple <code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code> directives may be used to
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd specify a number of addresses and ports to listen on. The
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd server will respond to requests from any of the listed
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd addresses and ports.</p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <p>For example, to make the server accept connections on both
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd port 80 and port 8000, on all interfaces, use:</p>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
3b3b7fc78d1f5bfc2769903375050048ff41ff26nd <div class="example"><p><code>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd Listen 80<br />
3b3b7fc78d1f5bfc2769903375050048ff41ff26nd Listen 8000
35714556a25fceb7c9bf9c4e01791b2e2a4c27c3nd </code></p></div>
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd
c82fca6d3f5608b946f18d37e8710b1d71e3478dnd <p>To make the server accept connections on port 80 for one interface,
and port 8000 on another, use</p>
<div class="example"><p><code>
Listen 192.0.2.1:80<br />
Listen 192.0.2.5:8000
</code></p></div>
<p>IPv6 addresses must be enclosed in square brackets, as in the
following example:</p>
<div class="example"><p><code>
Listen [2001:db8::a00:20ff:fea7:ccea]:80
</code></p></div>
<div class="warning"><p>Overlapping <code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code> directives will result in a
fatal error which will prevent the server from starting up.</p>
<div class="example"><p><code>
(48)Address already in use: make_sock: could not bind to address [::]:80
</code></p></div>
</div>
</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="section">
<h2><a name="ipv6" id="ipv6">Special IPv6 Considerations</a></h2>
<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,
allowing httpd to allocate IPv6 sockets, and to handle requests sent
over IPv6.</p>
<p>One complicating factor for httpd 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
platforms, but are disallowed by default on FreeBSD, NetBSD, and
OpenBSD, in order to match the system-wide policy on those
platforms. On systems where it is disallowed by default, a
special <code class="program"><a href="/programs/configure.html">configure</a></code> parameter can change this behavior
for httpd.</p>
<p>On the other hand, on some platforms, such as Linux and Tru64, the
<strong>only</strong> way to handle both IPv6 and IPv4 is to use
mapped addresses. If you want <code>httpd</code> 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>
<p><code>--enable-v4-mapped</code> is the default on all platforms except
FreeBSD, NetBSD, and OpenBSD, so this is probably how your httpd was
built.</p>
<p>If you want httpd to handle IPv4 connections only, regardless of
what your platform and APR will support, specify an IPv4 address on all
<code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code> directives, as in the
following examples:</p>
<div class="example"><p><code>
Listen 0.0.0.0:80<br />
Listen 192.0.2.1:80
</code></p></div>
<p>If your platform supports it and you want httpd to handle IPv4 and
IPv6 connections on separate sockets (i.e., to disable IPv4-mapped
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="protocol" id="protocol">Specifying the protocol with Listen</a></h2>
<p>The optional second <var>protocol</var> argument of
<code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code>
is not required for most
configurations. If not specified, <code>https</code> is the default for
port 443 and <code>http</code> the default for all other ports. The
protocol is used to determine which module should handle a request, and
to apply protocol specific optimizations with the
<code class="directive"><a href="/mod/core.html#acceptfilter">AcceptFilter</a></code> directive.</p>
<p>You only need to set the protocol if you are running on non-standard
ports. For example, running an <code>https</code> site on port 8443:</p>
<div class="example"><p><code>
Listen 192.170.2.1:8443 https
</code></p></div>
</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>
<p> The <code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code> directive does not implement
Virtual Hosts - it only tells the
main server what addresses and ports to listen on. If no
<code class="directive"><a href="/mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code>
directives are used, the server will behave
in the same way for all accepted requests. However,
<code class="directive"><a href="/mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code>
can be used to specify a different behavior
for one or more of the addresses or ports. To implement a
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
should be created for the specified address and port to set the
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
server is not listening to, it cannot be accessed.</p>
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="/de/bind.html" hreflang="de" rel="alternate" title="Deutsch">&nbsp;de&nbsp;</a> |
<a href="/en/bind.html" title="English">&nbsp;en&nbsp;</a> |
<a href="/fr/bind.html" hreflang="fr" rel="alternate" title="Fran�ais">&nbsp;fr&nbsp;</a> |
<a href="/ja/bind.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
<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><div id="footer">
<p class="apache">Copyright 2011 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p></div>
</body></html>