update xforms

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1178089 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 29 insertions, 29 deletions

diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en
index 79b27fada3..43224bd104 100644
--- a/docs/manual/bind.html.en
+++ b/docs/manual/bind.html.en
@@ -44,10 +44,10 @@
     <p>When httpd 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 
-    <a href="vhosts.html">Virtual Host</a> feature, which determines how 
-    <code>httpd</code> responds to different IP addresses, hostnames and 
+    be told to listen on specific ports, or only on selected
+    addresses, or a combination of both. This is often combined with the
+    <a href="vhosts.html">Virtual Host</a> feature, which determines how
+    <code>httpd</code> responds to different IP addresses, hostnames and
     ports.</p>
 
     <p>The <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code>
@@ -55,7 +55,7 @@
     incoming requests only on the specified port(s) or
     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 listens to the given port on all interfaces. 
+    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 <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code> directives may be used to
     specify a number of addresses and ports to listen on. The
@@ -85,9 +85,9 @@
       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 
+    <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>
@@ -100,31 +100,31 @@
 
     <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 
+    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 
+    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 
+    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 
+    <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 
+    <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 
+    <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>
 
@@ -133,8 +133,8 @@
       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 
+    <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>
@@ -143,14 +143,14 @@
     
     <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 
+       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 
+       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 
+    <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>
@@ -161,7 +161,7 @@
 <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 
+    <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>