|
Apache HTTP Server Version 2.2   BindingConfiguring Apache to listen on specific addresses and ports. See also Overview
When Apache starts, it binds 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 may need to be told to listen on specific ports, or only on selected addresses, or a combination of both. This is often combined with the Virtual Host feature, which determines how Apache responds to different IP addresses, hostnames and ports. The For example, to make the server accept connections on both port 80 and port 8000, on all interfaces, use:
To make the server accept connections on port 80 for one interface, and port 8000 on another, use
IPv6 addresses must be enclosed in square brackets, as in the following example:
Special IPv6 ConsiderationsA growing number of platforms implement IPv6, and APR supports IPv6 on most of these platforms, allowing Apache to allocate IPv6 sockets, and to handle requests sent over IPv6. 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
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 On the other hand, on some platforms, such as Linux and Tru64, the
only 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
If you want Apache to handle IPv4 connections only, regardless of
what your platform and APR will support, specify an IPv4 address on all
If your platform supports it and you want Apache to handle IPv4 and
IPv6 connections on separate sockets (i.e., to disable IPv4-mapped
addresses), specify the How This Works With Virtual HostsTheListen directive does not implement
Virtual Hosts - it only tells the
main server what addresses and ports to listen on. If no
<VirtualHost>
directives are used, the server will behave
in the same way for all accepted requests. However,
<VirtualHost>
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
<VirtualHost> section
should be created for the specified address and port to set the
behavior of this virtual host. Note that if the
<VirtualHost>
is set for an address and port that the
server is not listening to, it cannot be accessed.
|
