1
0
mirror of https://github.com/apache/httpd.git synced 2025-05-30 01:07:09 +03:00
apache/docs/manual/bind.html
Justin Erenkrantz cef27f2314 Remove all references to the Port directive and replace it with
appropriate links to the Listen directive.

If I had known that so many files had the Port directive in it, I would
have bundled this up as one big commit.  *sigh*  I just kept looking
and finding new files, fixing, and committing.  So, this should be the
rest of them for now.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91571 13f79535-47bb-0310-9956-ffa450edef68
2001-10-19 06:05:39 +00:00

76 lines
3.0 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>Setting which addresses and ports Apache uses</title>
</head>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
<body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#000080" alink="#FF0000">
<!--#include virtual="header.html" -->
<h1 align="CENTER">Setting which addresses and ports Apache
uses</h1>
<p>When Apache starts, it connects to some port and address on
the local machine and waits for incoming requests. By default,
it listens to all addresses on the machine. However, it needs to
be told to listen to specific ports, or to listen to only selected
addresses, or a combination. This is often combined with the
Virtual Host feature which determines how Apache responds to
different IP addresses, hostnames and ports.</p>
<p>The <code>Listen</code> directive tells the server to accept
incoming requests only on the specified port or
address-and-port combinations. If only a port number is
specified in the <code>Listen</code> directive, the server
listens to the given port on all interfaces. If an IP address
is given as well as a port, the server will listen on the given
port and interface. Multiple Listen directives may be used to
specify a number of addresses and ports to listen to. The
server will respond to requests from any of the listed
addresses and ports.</p>
<p>For example, to make the server accept connections on both
port 80 and port 8000, use:</p>
<pre>
Listen 80
Listen 8000
</pre>
To make the server accept connections on two specified
interfaces and port numbers, use
<pre>
Listen 192.170.2.1:80
Listen 192.170.2.5:8000
</pre>
<h2>How this works with Virtual Hosts</h2>
<p>Listen does not implement Virtual Hosts. It only tells the
main server what addresses and ports to listen to. If no
&lt;VirtualHost&gt; directives are used, the server will behave
the same for all accepted requests. However,
&lt;VirtualHost&gt; can be used to specify a different behavior
for one or more of the addresses and ports. To implement a
VirtualHost, the server must first be told to listen to the
address and port to be used. Then a &lt;VirtualHost&gt; section
should be created for a specified address and port to set the
behavior of this virtual host. Note that if the
&lt;VirtualHost&gt; is set for an address and port that the
server is not listening to, it cannot be accessed.</p>
<h2>See also</h2>
See also the documentation on <a
href="mod/mpm_common.html#listen">Listen directive</a>, <a
href="vhosts/">Virtual Hosts</a>, <a
href="dns-caveats.html">DNS Issues</a> and <a
href="mod/core.html#virtualhost">&lt;VirtualHost&gt;
section</a>. <!--#include virtual="footer.html" -->
</body>
</html>