From: Noirin Plunkett Date: Mon, 23 Jan 2006 16:43:16 +0000 (+0000) Subject: Minor language fixes X-Git-Tag: 2.3.0~2582 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ce4b622c5856c4056fcb4e11a6efc374a68780be;p=thirdparty%2Fapache%2Fhttpd.git Minor language fixes git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@371589 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/bind.xml b/docs/manual/bind.xml index a760d07d7aa..b9b2c16baa8 100644 --- a/docs/manual/bind.xml +++ b/docs/manual/bind.xml @@ -48,15 +48,15 @@

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 needs to - be told to listen on specific ports, or to listen on only selected - addresses, or a combination. This is often combined with the - Virtual Host feature which determines how Apache responds to + 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 Listen directive tells the server to accept - incoming requests only on the specified port or + incoming requests only on the specified ports or address-and-port combinations. If only a port number is specified in the Listen directive, the server @@ -69,22 +69,22 @@ addresses and ports.

For example, to make the server accept connections on both - port 80 and port 8000, use:

+ port 80 and port 8000, on all interfaces, use:

Listen 80
Listen 8000 -

To make the server accept connections on two specified - interfaces and port numbers, use

+

To make the server accept connections on port 80 for one interface, + and port 8080 on another, use

Listen 192.170.2.1:80
Listen 192.170.2.5:8000 -

IPv6 addresses must be surrounded in square brackets, as in the +

IPv6 addresses must be enclosed in square brackets, as in the following example:

@@ -97,27 +97,27 @@

A growing number of platforms implement IPv6, and APR supports IPv6 on most of these platforms, - allowing Apache to allocate IPv6 sockets and handle requests which - were sent over IPv6.

+ 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. But even on systems where it is disallowed by default, a + 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 configure parameter can change this behavior for Apache.

-

On the other hand, on some platforms such as Linux and Tru64 the +

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 --enable-v4-mapped configure option.

-

--enable-v4-mapped is the default on all platforms but +

--enable-v4-mapped is the default on all platforms except FreeBSD, NetBSD, and OpenBSD, so this is probably how your Apache was built.

@@ -132,7 +132,7 @@

If your platform supports it and you want Apache to handle IPv4 and - IPv6 connections on separate sockets (i.e., to disable IPv4-mapped + IPv6 connections on separate sockets (i.e., to disable IPv4-mapped addresses), specify the --disable-v4-mapped configure option. --disable-v4-mapped is the default on FreeBSD, NetBSD, and OpenBSD.

@@ -141,20 +141,20 @@
How This Works With Virtual Hosts -

Listen does not implement - Virtual Hosts. It only tells the - main server what addresses and ports to listen to. If no +

The Listen 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 - the same for all accepted requests. However, + 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 and ports. To implement a + 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 a specified address and port to set the + 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