httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gry...@apache.org
Subject svn commit: r1049240 - in /httpd/httpd/trunk/docs/manual/mod: core.html.en core.xml
Date Tue, 14 Dec 2010 20:03:01 GMT
Author: gryzor
Date: Tue Dec 14 20:03:01 2010
New Revision: 1049240

URL: http://svn.apache.org/viewvc?rev=1049240&view=rev
Log:
Removes the ":80" from the sole ServerName example of the documentation, as it is a dumb "default".

Modified:
    httpd/httpd/trunk/docs/manual/mod/core.html.en
    httpd/httpd/trunk/docs/manual/mod/core.xml

Modified: httpd/httpd/trunk/docs/manual/mod/core.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.html.en?rev=1049240&r1=1049239&r2=1049240&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.html.en Tue Dec 14 20:03:01 2010
@@ -122,11 +122,11 @@ On Windows from Apache httpd 2.3.3 and l
        The basic premise is for the kernel to not send a socket to the server
        process until either data is received or an entire HTTP Request is buffered.
        Only <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&amp;sektion=9">
-       FreeBSD's Accept Filters</a>, Linux's more primitive 
+       FreeBSD's Accept Filters</a>, Linux's more primitive
        <code>TCP_DEFER_ACCEPT</code>, and Windows' optimized AcceptEx()
        are currently supported.</p>
 
-    <p>Using <code>none</code> for an argument will disable any accept filters 
+    <p>Using <code>none</code> for an argument will disable any accept filters
        for that protocol.  This is useful for protocols that require a server
        send data first, such as <code>ftp:</code> or <code>nntp</code>:</p>
     <div class="example"><p><code>AcceptFilter nntp none</code></p></div>
@@ -142,12 +142,12 @@ On Windows from Apache httpd 2.3.3 and l
         AcceptFilter http httpready <br />
         AcceptFilter https dataready
     </code></p></div>
-    
+
     <p>The <code>httpready</code> accept filter buffers entire HTTP requests at
-       the kernel level.  Once an entire request is received, the kernel then 
-       sends it to the server. See the 
+       the kernel level.  Once an entire request is received, the kernel then
+       sends it to the server. See the
        <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&amp;sektion=9">
-       accf_http(9)</a> man page for more details.  Since HTTPS requests are 
+       accf_http(9)</a> man page for more details.  Since HTTPS requests are
        encrypted only the <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&amp;sektion=9">
        accf_data(9)</a> filter is used.</p>
 
@@ -158,9 +158,9 @@ On Windows from Apache httpd 2.3.3 and l
     </code></p></div>
 
     <p>Linux's <code>TCP_DEFER_ACCEPT</code> does not support buffering http
-       requests.  Any value besides <code>none</code> will enable 
+       requests.  Any value besides <code>none</code> will enable
        <code>TCP_DEFER_ACCEPT</code> on that listener. For more details
-       see the Linux 
+       see the Linux
        <a href="http://homepages.cwi.nl/~aeb/linux/man2html/man7/tcp.7.html">
        tcp(7)</a> man page.</p>
 
@@ -185,7 +185,7 @@ On Windows from Apache httpd 2.3.3 and l
        and will not recycle sockets between connections.  This is useful for
        network adapters with broken driver support, as well as some virtual
        network providers such as vpn drivers, or spam, virus or spyware
-       filters.</p>  
+       filters.</p>
 
 
 <h3>See also</h3>
@@ -481,7 +481,7 @@ be passed through</td></tr>
     server error.</p>
 
     <div class="note"><p>For security and performance reasons, do not set
-    <code>AllowOverride</code> to anything other than <code>None</code> 
+    <code>AllowOverride</code> to anything other than <code>None</code>
     in your <code>&lt;Directory /&gt;</code> block. Instead, find (or
     create) the <code>&lt;Directory&gt;</code> block that refers to the
     directory where you're actually planning to place a
@@ -618,7 +618,7 @@ named file-system directory, sub-directo
     <p><code class="directive">&lt;Directory&gt;</code> and
     <code>&lt;/Directory&gt;</code> are used to enclose a group of
     directives that will apply only to the named directory,
-    sub-directories of that directory, and the files within the respective 
+    sub-directories of that directory, and the files within the respective
     directories.  Any directive that is allowed
     in a directory context may be used. <var>Directory-path</var> is
     either the full path to a directory, or a wild-card string using
@@ -757,9 +757,9 @@ the contents of file-system directories 
 </table>
     <p><code class="directive">&lt;DirectoryMatch&gt;</code> and
     <code>&lt;/DirectoryMatch&gt;</code> are used to enclose a group
-    of directives which will apply only to the named directory (and the files within), 
-    the same as <code class="directive"><a href="#directory">&lt;Directory&gt;</a></code>. 
-    However, it takes as an argument a 
+    of directives which will apply only to the named directory (and the files within),
+    the same as <code class="directive"><a href="#directory">&lt;Directory&gt;</a></code>.
+    However, it takes as an argument a
     <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>.  For example:</p>
 
     <div class="example"><p><code>
@@ -778,8 +778,8 @@ the contents of file-system directories 
     </div>
 
     <div class="note"><h3>Trailing Slash</h3>
-      This directive applies to requests for directories that may or may 
-      not end in a trailing slash, so expressions that are anchored to the 
+      This directive applies to requests for directories that may or may
+      not end in a trailing slash, so expressions that are anchored to the
       end of line ($) must be written with care.
     </div>
 
@@ -815,7 +815,7 @@ from the web</td></tr>
 
     <p>then an access to
     <code>http://my.example.com/index.html</code> refers to
-    <code>/usr/web/index.html</code>. If the <var>directory-path</var> is 
+    <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
     not absolute then it is assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
 
     <p>The <code class="directive">DocumentRoot</code> should be specified without
@@ -1067,7 +1067,7 @@ in case of an error</td></tr>
     will be immediately halted and the internal error message returned.
     This is necessary to guard against security problems caused by
     bad requests.</p>
-   
+
     <p>If you are using mod_proxy, you may wish to enable
     <code class="directive"><a href="../mod/mod_proxy.html#proxyerroroverride">ProxyErrorOverride</a></code> so that you can provide
     custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride,
@@ -1091,7 +1091,7 @@ in case of an error</td></tr>
 </table>
     <p>The <code class="directive">ErrorLog</code> directive sets the name of
     the file to which the server will log any errors it encounters. If
-    the <var>file-path</var> is not absolute then it is assumed to be 
+    the <var>file-path</var> is not absolute then it is assumed to be
     relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
 
     <div class="example"><h3>Example</h3><p><code>
@@ -1129,7 +1129,7 @@ in case of an error</td></tr>
     <div class="warning"><h3>Note</h3>
       <p>When entering a file path on non-Unix platforms, care should be taken
       to make sure that only forward slashes are used even though the platform
-      may allow the use of back slashes. In general it is a good idea to always 
+      may allow the use of back slashes. In general it is a good idea to always
       use forward slashes throughout the configuration files.</p>
     </div>
 
@@ -1286,7 +1286,7 @@ in case of an error</td></tr>
 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="directive-section"><h2><a name="ExtendedStatus" id="ExtendedStatus">ExtendedStatus</a> <a name="extendedstatus" id="extendedstatus">Directive</a></h2>
 <table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Keep track of extended status information for each 
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Keep track of extended status information for each
 request</td></tr>
 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>ExtendedStatus On|Off</code></td></tr>
 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>ExtendedStatus Off[*]</code></td></tr>
@@ -1295,8 +1295,8 @@ request</td></tr>
 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
 </table>
     <p>This option tracks additional data per worker about the
-    currently executing request, and a utilization summary; you 
-    can see these variables during runtime by configuring 
+    currently executing request, and a utilization summary; you
+    can see these variables during runtime by configuring
     <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>.  Note that other modules may
     rely on this scoreboard.</p>
 
@@ -1307,7 +1307,7 @@ request</td></tr>
     during a graceful restart.</p>
 
     <div class="note">
-    <p>Note that loading <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> will change 
+    <p>Note that loading <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> will change
     the default behavior to ExtendedStatus On, while other
     third party modules may do the same.  Such modules rely on
     collecting detailed information about the state of all workers.
@@ -1375,8 +1375,8 @@ HTTP response header for static files</t
     changed via <code class="directive">FileETag</code>.
     </div>
     <div class="note"><h3>Server Side Includes</h3>
-    An ETag is not generated for responses parsed by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>, 
-    since the response entity can change without a change of the INode, MTime, or Size 
+    An ETag is not generated for responses parsed by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>,
+    since the response entity can change without a change of the INode, MTime, or Size
     of the static file with embedded SSI directives.
     </div>
 
@@ -1411,7 +1411,7 @@ filenames</td></tr>
     <p>The <var>filename</var> argument should include a filename, or
     a wild-card string, where <code>?</code> matches any single character,
     and <code>*</code> matches any sequences of characters.
-    <a class="glossarylink" href="../glossary.html#regex" title="see glossary">Regular expressions</a> 
+    <a class="glossarylink" href="../glossary.html#regex" title="see glossary">Regular expressions</a>
     can also be used, with the addition of the
     <code>~</code> character. For example:</p>
 
@@ -1448,7 +1448,7 @@ filenames</td></tr>
     <p>The <code class="directive">&lt;FilesMatch&gt;</code> directive
     limits the scope of the enclosed directives by filename, just as the
     <code class="directive"><a href="#files">&lt;Files&gt;</a></code> directive
-    does. However, it accepts a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular 
+    does. However, it accepts a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular
     expression</a>. For example:</p>
 
     <div class="example"><p><code>
@@ -1515,8 +1515,8 @@ media type in the HTTP Content-Type head
     </code></p></div>
 
     <p>This directive primarily overrides the content types generated for
-    static files served out of the filesystem.  For resources other than 
-    static files, where the generator of the response typically specifies 
+    static files served out of the filesystem.  For resources other than
+    static files, where the generator of the response typically specifies
     a Content-Type, this directive has no effect.</p>
 
 
@@ -1536,7 +1536,7 @@ media type in the HTTP Content-Type head
     argument ends with a percent symbol ('%'), subdirectories are created
     for each process id.</p>
 
-    <p>This directive currently only works with the <code class="module"><a href="../mod/prefork.html">prefork</a></code> 
+    <p>This directive currently only works with the <code class="module"><a href="../mod/prefork.html">prefork</a></code>
     MPM.</p>
 
 </div>
@@ -1796,7 +1796,7 @@ wildcard matching available in 2.3.6 and
     <code class="directive"><a href="#include">Include</a></code> directive will fail with an
     error saying the file or directory cannot be found.</p>
 
-    <p>The file path specified may be an absolute path, or may be relative 
+    <p>The file path specified may be an absolute path, or may be relative
     to the <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory.</p>
 
     <p>Examples:</p>
@@ -1817,7 +1817,7 @@ wildcard matching available in 2.3.6 and
     path. In the following example, the server will fail to load if no
     directories match conf/vhosts/*, but will load successfully if no
     files match *.conf.</p>
-  
+
     <div class="example"><p><code>
       Include conf/vhosts/*/vhost.conf<br />
       Include conf/vhosts/*/*.conf
@@ -1829,7 +1829,7 @@ wildcard matching available in 2.3.6 and
     <div class="example"><p><code>
       Include strict conf/vhosts/*/*.conf
     </code></p></div>
-  
+
     <p>In this example, the server load successfully if either conf/vhosts/*
     matches no directories, or if *.conf matches no files:</p>
 
@@ -1892,7 +1892,7 @@ requests on a persistent connection</td>
 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host</td></tr>
 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Specifying a value in milliseconds is available in 
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Specifying a value in milliseconds is available in
 Apache httpd 2.3.2 and later</td></tr>
 </table>
     <p>The number of seconds Apache httpd will wait for a subsequent
@@ -1905,7 +1905,7 @@ Apache httpd 2.3.2 and later</td></tr>
     may cause performance problems in heavily loaded servers. The
     higher the timeout, the more server processes will be kept
     occupied waiting on connections with idle clients.</p>
-    
+
     <p>In a name-based virtual host context, the value of the first
     defined virtual host (the default host) in a set of <code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code> will be used.
     The other values will be ignored.</p>
@@ -1983,12 +1983,12 @@ methods</td></tr>
       &lt;LimitExcept GET&gt;
       <span class="indent">
         Require valid-user
-      </span> 
+      </span>
       &lt;/LimitExcept&gt;<br />
       &lt;Limit POST&gt;
       <span class="indent">
         Require group editors
-      </span> 
+      </span>
       &lt;/Limit&gt;
     </code></p></div>
 
@@ -2101,8 +2101,8 @@ from the client</td></tr>
     <div class="example"><p><code>
       LimitRequestBody 102400
     </code></p></div>
-    
-    <div class="note"><p>For a full description of how this directive is interpreted by 
+
+    <div class="note"><p>For a full description of how this directive is interpreted by
     proxy requests, see the <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> documentation.</p>
     </div>
 
@@ -2149,7 +2149,7 @@ will be accepted from the client</td></t
     </code></p></div>
 
      <div class="warning"><h3>Warning</h3>
-     <p> When name-based virtual hosting is used, the value for this 
+     <p> When name-based virtual hosting is used, the value for this
      directive is taken from the default (first-listed) virtual host for the
      <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
      </div>
@@ -2171,11 +2171,11 @@ client</td></tr>
     that will be allowed in an HTTP request header.</p>
 
     <p>The <code class="directive">LimitRequestFieldSize</code> directive
-    allows the server administrator to reduce or increase the limit 
+    allows the server administrator to reduce or increase the limit
     on the allowed size of an HTTP request header field. A server
-    needs this value to be large enough to hold any one header field 
-    from a normal client request. The size of a normal request header 
-    field will vary greatly among different client implementations, 
+    needs this value to be large enough to hold any one header field
+    from a normal client request. The size of a normal request header
+    field will vary greatly among different client implementations,
     often depending upon the extent to which a user has configured
     their browser to support detailed content negotiation. SPNEGO
     authentication headers can be up to 12392 bytes.</p>
@@ -2194,7 +2194,7 @@ client</td></tr>
     the default.</div>
 
     <div class="warning"><h3>Warning</h3>
-    <p> When name-based virtual hosting is used, the value for this 
+    <p> When name-based virtual hosting is used, the value for this
     directive is taken from the default (first-listed) virtual host for the
     <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
     </div>
@@ -2212,7 +2212,7 @@ from the client</td></tr>
 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
 </table>
-    <p>This directive sets the number of <var>bytes</var> that will be 
+    <p>This directive sets the number of <var>bytes</var> that will be
     allowed on the HTTP request-line.</p>
 
     <p>The <code class="directive">LimitRequestLine</code> directive allows
@@ -2239,7 +2239,7 @@ from the client</td></tr>
     the default.</div>
 
     <div class="warning"><h3>Warning</h3>
-    <p> When name-based virtual hosting is used, the value for this 
+    <p> When name-based virtual hosting is used, the value for this
     directive is taken from the default (first-listed) virtual host for the
     <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
     </div>
@@ -2300,26 +2300,26 @@ URLs</td></tr>
     <ul>
       <li>The specified location matches exactly the path component of the URL.
       </li>
-      <li>The specified location, which ends in a forward slash, is a prefix 
+      <li>The specified location, which ends in a forward slash, is a prefix
       of the path component of the URL (treated as a context root).
       </li>
-      <li>The specified location, with the addition of a trailing slash, is a 
+      <li>The specified location, with the addition of a trailing slash, is a
       prefix of the path component of the URL (also treated as a context root).
       </li>
     </ul>
     <p>
-    In the example below, where no trailing slash is used, requests to 
+    In the example below, where no trailing slash is used, requests to
     /private1, /private1/ and /private1/file.txt will have the enclosed
-    directives applied, but /private1other would not. 
+    directives applied, but /private1other would not.
     </p>
     <div class="example"><p><code>
       &lt;Location /private1&gt;
           ...
     </code></p></div>
     <p>
-    In the example below, where a trailing slash is used, requests to 
+    In the example below, where a trailing slash is used, requests to
     /private2/ and /private2/file.txt will have the enclosed
-    directives applied, but /private2 and /private2other would not. 
+    directives applied, but /private2 and /private2other would not.
     </p>
     <div class="example"><p><code>
       &lt;Location /private2<em>/</em>&gt;
@@ -2331,7 +2331,7 @@ URLs</td></tr>
     <p>Use <code class="directive">&lt;Location&gt;</code> to apply
     directives to content that lives outside the filesystem.  For
     content that lives in the filesystem, use <code class="directive"><a href="#directory">&lt;Directory&gt;</a></code> and <code class="directive"><a href="#files">&lt;Files&gt;</a></code>.  An exception is
-    <code>&lt;Location /&gt;</code>, which is an easy way to 
+    <code>&lt;Location /&gt;</code>, which is an easy way to
     apply a configuration to the entire server.</p>
     </div>
 
@@ -2347,7 +2347,7 @@ URLs</td></tr>
     characters. Neither wildcard character matches a / in the URL-path.</p>
 
     <p><a class="glossarylink" href="../glossary.html#regex" title="see glossary">Regular expressions</a>
-    can also be used, with the addition of the <code>~</code> 
+    can also be used, with the addition of the <code>~</code>
     character. For example:</p>
 
     <div class="example"><p><code>
@@ -2709,7 +2709,7 @@ or specified mutexes</td></tr>
         <li><code>default | yes</code>
         <p>This selects the default locking implementation, as determined by
         <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a>.  The default locking implementation can
-        be displayed by running <code class="program"><a href="../programs/httpd.html">httpd</a></code> with the 
+        be displayed by running <code class="program"><a href="../programs/httpd.html">httpd</a></code> with the
         <code>-V</code> option.</p></li>
 
         <li><code>none | no</code>
@@ -2730,7 +2730,7 @@ or specified mutexes</td></tr>
         <p>This is a mutex variant based on a SystemV IPC semaphore.</p>
 
         <div class="warning"><h3>Warning</h3>
-        <p>It is possible to "leak" SysV semaphores if processes crash 
+        <p>It is possible to "leak" SysV semaphores if processes crash
         before the semaphore is removed.</p>
 	</div>
 
@@ -2765,7 +2765,7 @@ or specified mutexes</td></tr>
         </li>
 
         <li><code>fcntl:/path/to/mutex</code>
-        <p>This is a mutex variant where a physical (lock-)file and the 
+        <p>This is a mutex variant where a physical (lock-)file and the
         <code>fcntl()</code> function are used as the mutex.</p>
 
         <div class="warning"><h3>Warning</h3>
@@ -2787,10 +2787,10 @@ or specified mutexes</td></tr>
         order.</p></li>
     </ul>
 
-    <p>Most mechanisms are only available on selected platforms, where the 
+    <p>Most mechanisms are only available on selected platforms, where the
     underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="see glossary">APR</a> support it.  Mechanisms
     which aren't available on all platforms are <em>posixsem</em>,
-    <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>, 
+    <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>,
     <em>flock</em>, and <em>file</em>.</p>
 
     <p>With the file-based mechanisms <em>fcntl</em> and <em>flock</em>,
@@ -2800,12 +2800,12 @@ or specified mutexes</td></tr>
     filesystem for <code>/path/to/mutex</code> and never a directory residing
     on a NFS- or AFS-filesystem.  The basename of the file will be the mutex
     type, an optional instance string provided by the module, and unless the
-    <code>OmitPID</code> keyword is specified, the process id of the httpd 
+    <code>OmitPID</code> keyword is specified, the process id of the httpd
     parent process will be appended to to make the file name unique, avoiding
     conflicts when multiple httpd instances share a lock file directory.  For
     example, if the mutex name is <code>mpm-accept</code> and the lock file
     directory is <code>/var/httpd/locks</code>, the lock file name for the
-    httpd instance with parent process id 12345 would be 
+    httpd instance with parent process id 12345 would be
     <code>/var/httpd/locks/mpm-accept.12345</code>.</p>
 
     <div class="warning"><h3>Security</h3>
@@ -2896,15 +2896,15 @@ hosting</td></tr>
 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
 </table>
 
-<p>A single <code class="directive">NameVirtualHost</code> directive 
-identifies a set of identical virtual hosts on which the server will  
-further select from on the basis of the <em>hostname</em> 
+<p>A single <code class="directive">NameVirtualHost</code> directive
+identifies a set of identical virtual hosts on which the server will
+further select from on the basis of the <em>hostname</em>
 requested by the client.  The <code class="directive">NameVirtualHost</code>
-directive is a required directive if you want to configure 
+directive is a required directive if you want to configure
 <a href="../vhosts/">name-based virtual hosts</a>.</p>
 
 <p>This directive, and the corresponding <code class="directive">VirtualHost</code>,
-<em>must</em> be qualified with a port number if the server supports both HTTP 
+<em>must</em> be qualified with a port number if the server supports both HTTP
 and HTTPS connections.</p>
 
 <p>Although <var>addr</var> can be a hostname, it is recommended
@@ -2912,16 +2912,16 @@ that you always use an IP address or a w
 NameVirtualHost matches only virtualhosts that also have a literal wildcard
 as their argument.</p>
 
-<p>In cases where a firewall or other proxy receives the requests and 
+<p>In cases where a firewall or other proxy receives the requests and
 forwards them on a different IP address to the server, you must specify the
 IP address of the physical interface on the machine which will be
 servicing the requests. </p>
 
-<p> In the example below, requests received on interface 192.0.2.1 and port 80 
+<p> In the example below, requests received on interface 192.0.2.1 and port 80
 will only select among the first two virtual hosts. Requests received on
 port 80 on any other interface will only select among the third and fourth
-virtual hosts. In the common case where the interface isn't important 
-to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives 
+virtual hosts. In the common case where the interface isn't important
+to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives
 are necessary.</p>
 
    <div class="example"><p><code>
@@ -3365,7 +3365,7 @@ of a request or the last 63, assuming th
 <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache httpd 2.2.7 and later.</td></tr>
 </table>
     <p>mod_status with <code>ExtendedStatus On</code>
-    displays the actual request being handled. 
+    displays the actual request being handled.
     For historical purposes, only 63 characters of the request
     are actually stored for display purposes. This directive
     controls whether the 1st 63 characters are stored (the previous
@@ -3467,7 +3467,7 @@ itself</td></tr>
     <p>Additionally, <code class="directive">ServerName</code> is used (possibly
     in conjunction with <code class="directive">ServerAlias</code>) to uniquely
     identify a virtual host, when using <a href="../vhosts/name-based.html">name-based virtual hosts</a>.</p>
-    
+
     <p>For example, if the name of the
     machine hosting the web server is <code>simple.example.com</code>,
     but the machine also has the DNS alias <code>www.example.com</code>
@@ -3475,7 +3475,7 @@ itself</td></tr>
     directive should be used:</p>
 
     <div class="example"><p><code>
-      ServerName www.example.com:80
+      ServerName www.example.com
     </code></p></div>
 
     <p>The <code class="directive">ServerName</code> directive
@@ -3503,7 +3503,7 @@ itself</td></tr>
     <code>https://</code> scheme and the port number to which the
     clients connect in the <code class="directive">ServerName</code> directive
     to make sure that the server generates the correct
-    self-referential URLs. 
+    self-referential URLs.
     </p>
 
     <p>See the description of the
@@ -3569,7 +3569,7 @@ is accessed by an incompatible browser</
     <p>The <code class="directive">ServerRoot</code> directive sets the
     directory in which the server lives. Typically it will contain the
     subdirectories <code>conf/</code> and <code>logs/</code>. Relative
-    paths in other configuration directives (such as <code class="directive"><a href="#include">Include</a></code> or <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>, for example) are taken as 
+    paths in other configuration directives (such as <code class="directive"><a href="#include">Include</a></code> or <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>, for example) are taken as
     relative to this directory.</p>
 
     <div class="example"><h3>Example</h3><p><code>
@@ -3676,7 +3676,7 @@ header</td></tr>
 
     <p>After version 2.0.44, this directive also controls the
     information presented by the <code class="directive"><a href="#serversignature">ServerSignature</a></code> directive.</p>
-    
+
     <div class="note">Setting <code class="directive">ServerTokens</code> to less than
     <code>minimal</code> is not recommended because it makes it more
     difficult to debug interoperational problems. Also note that
@@ -3862,7 +3862,7 @@ certain events before failing a request<
     allowed) error to the client.</p>
 
     <p>Finally, for testing and diagnostic purposes only, request
-    bodies may be allowed using the non-compliant <code>TraceEnable 
+    bodies may be allowed using the non-compliant <code>TraceEnable
     extended</code> directive.  The core (as an origin server) will
     restrict the request body to 64k (plus 8k for chunk headers if
     <code>Transfer-Encoding: chunked</code> is used).  The core will
@@ -3985,7 +3985,7 @@ port</td></tr>
       <li>Port provided in <code>Servername</code></li>
       <li>Default port</li>
      </ul>
-    
+
     <p>With <code>UseCanonicalPhysicalPort Off</code>, the
     physical ports are removed from the ordering.</p>
     </div>

Modified: httpd/httpd/trunk/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.xml?rev=1049240&r1=1049239&r2=1049240&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.xml Tue Dec 14 20:03:01 2010
@@ -41,11 +41,11 @@ On Windows from Apache httpd 2.3.3 and l
        The basic premise is for the kernel to not send a socket to the server
        process until either data is received or an entire HTTP Request is buffered.
        Only <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&amp;sektion=9">
-       FreeBSD's Accept Filters</a>, Linux's more primitive 
+       FreeBSD's Accept Filters</a>, Linux's more primitive
        <code>TCP_DEFER_ACCEPT</code>, and Windows' optimized AcceptEx()
        are currently supported.</p>
 
-    <p>Using <code>none</code> for an argument will disable any accept filters 
+    <p>Using <code>none</code> for an argument will disable any accept filters
        for that protocol.  This is useful for protocols that require a server
        send data first, such as <code>ftp:</code> or <code>nntp</code>:</p>
     <example>AcceptFilter nntp none</example>
@@ -61,12 +61,12 @@ On Windows from Apache httpd 2.3.3 and l
         AcceptFilter http httpready <br/>
         AcceptFilter https dataready
     </example>
-    
+
     <p>The <code>httpready</code> accept filter buffers entire HTTP requests at
-       the kernel level.  Once an entire request is received, the kernel then 
-       sends it to the server. See the 
+       the kernel level.  Once an entire request is received, the kernel then
+       sends it to the server. See the
        <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&amp;sektion=9">
-       accf_http(9)</a> man page for more details.  Since HTTPS requests are 
+       accf_http(9)</a> man page for more details.  Since HTTPS requests are
        encrypted only the <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&amp;sektion=9">
        accf_data(9)</a> filter is used.</p>
 
@@ -77,9 +77,9 @@ On Windows from Apache httpd 2.3.3 and l
     </example>
 
     <p>Linux's <code>TCP_DEFER_ACCEPT</code> does not support buffering http
-       requests.  Any value besides <code>none</code> will enable 
+       requests.  Any value besides <code>none</code> will enable
        <code>TCP_DEFER_ACCEPT</code> on that listener. For more details
-       see the Linux 
+       see the Linux
        <a href="http://homepages.cwi.nl/~aeb/linux/man2html/man7/tcp.7.html">
        tcp(7)</a> man page.</p>
 
@@ -104,7 +104,7 @@ On Windows from Apache httpd 2.3.3 and l
        and will not recycle sockets between connections.  This is useful for
        network adapters with broken driver support, as well as some virtual
        network providers such as vpn drivers, or spam, virus or spyware
-       filters.</p>  
+       filters.</p>
 
 </usage>
 <seealso><directive>Protocol</directive></seealso>
@@ -425,7 +425,7 @@ be passed through</description>
     server error.</p>
 
     <note><p>For security and performance reasons, do not set
-    <code>AllowOverride</code> to anything other than <code>None</code> 
+    <code>AllowOverride</code> to anything other than <code>None</code>
     in your <code>&lt;Directory /&gt;</code> block. Instead, find (or
     create) the <code>&lt;Directory&gt;</code> block that refers to the
     directory where you're actually planning to place a
@@ -564,7 +564,7 @@ named file-system directory, sub-directo
     <p><directive type="section">Directory</directive> and
     <code>&lt;/Directory&gt;</code> are used to enclose a group of
     directives that will apply only to the named directory,
-    sub-directories of that directory, and the files within the respective 
+    sub-directories of that directory, and the files within the respective
     directories.  Any directive that is allowed
     in a directory context may be used. <var>Directory-path</var> is
     either the full path to a directory, or a wild-card string using
@@ -705,9 +705,9 @@ the contents of file-system directories 
 <usage>
     <p><directive type="section">DirectoryMatch</directive> and
     <code>&lt;/DirectoryMatch&gt;</code> are used to enclose a group
-    of directives which will apply only to the named directory (and the files within), 
-    the same as <directive module="core" type="section">Directory</directive>. 
-    However, it takes as an argument a 
+    of directives which will apply only to the named directory (and the files within),
+    the same as <directive module="core" type="section">Directory</directive>.
+    However, it takes as an argument a
     <glossary ref="regex">regular expression</glossary>.  For example:</p>
 
     <example>
@@ -726,8 +726,8 @@ the contents of file-system directories 
     </note>
 
     <note><title>Trailing Slash</title>
-      This directive applies to requests for directories that may or may 
-      not end in a trailing slash, so expressions that are anchored to the 
+      This directive applies to requests for directories that may or may
+      not end in a trailing slash, so expressions that are anchored to the
       end of line ($) must be written with care.
     </note>
 </usage>
@@ -762,8 +762,8 @@ from the web</description>
 
     <p>then an access to
     <code>http://my.example.com/index.html</code> refers to
-    <code>/usr/web/index.html</code>. If the <var>directory-path</var> is 
-    not absolute then it is assumed to be relative to the <directive 
+    <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
+    not absolute then it is assumed to be relative to the <directive
     module="core">ServerRoot</directive>.</p>
 
     <p>The <directive>DocumentRoot</directive> should be specified without
@@ -1019,7 +1019,7 @@ in case of an error</description>
     will be immediately halted and the internal error message returned.
     This is necessary to guard against security problems caused by
     bad requests.</p>
-   
+
     <p>If you are using mod_proxy, you may wish to enable
     <directive module="mod_proxy">ProxyErrorOverride</directive> so that you can provide
     custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride,
@@ -1041,7 +1041,7 @@ in case of an error</description>
 <usage>
     <p>The <directive>ErrorLog</directive> directive sets the name of
     the file to which the server will log any errors it encounters. If
-    the <var>file-path</var> is not absolute then it is assumed to be 
+    the <var>file-path</var> is not absolute then it is assumed to be
     relative to the <directive module="core">ServerRoot</directive>.</p>
 
     <example><title>Example</title>
@@ -1080,7 +1080,7 @@ in case of an error</description>
     <note type="warning"><title>Note</title>
       <p>When entering a file path on non-Unix platforms, care should be taken
       to make sure that only forward slashes are used even though the platform
-      may allow the use of back slashes. In general it is a good idea to always 
+      may allow the use of back slashes. In general it is a good idea to always
       use forward slashes throughout the configuration files.</p>
     </note>
 </usage>
@@ -1258,7 +1258,7 @@ in case of an error</description>
 
 <directivesynopsis>
 <name>ExtendedStatus</name>
-<description>Keep track of extended status information for each 
+<description>Keep track of extended status information for each
 request</description>
 <syntax>ExtendedStatus On|Off</syntax>
 <default>ExtendedStatus Off[*]</default>
@@ -1266,8 +1266,8 @@ request</description>
 
 <usage>
     <p>This option tracks additional data per worker about the
-    currently executing request, and a utilization summary; you 
-    can see these variables during runtime by configuring 
+    currently executing request, and a utilization summary; you
+    can see these variables during runtime by configuring
     <module>mod_status</module>.  Note that other modules may
     rely on this scoreboard.</p>
 
@@ -1278,7 +1278,7 @@ request</description>
     during a graceful restart.</p>
 
     <note>
-    <p>Note that loading <module>mod_status</module> will change 
+    <p>Note that loading <module>mod_status</module> will change
     the default behavior to ExtendedStatus On, while other
     third party modules may do the same.  Such modules rely on
     collecting detailed information about the state of all workers.
@@ -1348,8 +1348,8 @@ HTTP response header for static files</d
     changed via <directive>FileETag</directive>.
     </note>
     <note><title>Server Side Includes</title>
-    An ETag is not generated for responses parsed by <module>mod_include</module>, 
-    since the response entity can change without a change of the INode, MTime, or Size 
+    An ETag is not generated for responses parsed by <module>mod_include</module>,
+    since the response entity can change without a change of the INode, MTime, or Size
     of the static file with embedded SSI directives.
     </note>
 
@@ -1388,7 +1388,7 @@ filenames</description>
     <p>The <var>filename</var> argument should include a filename, or
     a wild-card string, where <code>?</code> matches any single character,
     and <code>*</code> matches any sequences of characters.
-    <glossary ref="regex">Regular expressions</glossary> 
+    <glossary ref="regex">Regular expressions</glossary>
     can also be used, with the addition of the
     <code>~</code> character. For example:</p>
 
@@ -1427,7 +1427,7 @@ filenames</description>
     <p>The <directive type="section">FilesMatch</directive> directive
     limits the scope of the enclosed directives by filename, just as the
     <directive module="core" type="section">Files</directive> directive
-    does. However, it accepts a <glossary ref="regex">regular 
+    does. However, it accepts a <glossary ref="regex">regular
     expression</glossary>. For example:</p>
 
     <example>
@@ -1492,8 +1492,8 @@ media type in the HTTP Content-Type head
     </example>
 
     <p>This directive primarily overrides the content types generated for
-    static files served out of the filesystem.  For resources other than 
-    static files, where the generator of the response typically specifies 
+    static files served out of the filesystem.  For resources other than
+    static files, where the generator of the response typically specifies
     a Content-Type, this directive has no effect.</p>
 
 </usage>
@@ -1512,7 +1512,7 @@ media type in the HTTP Content-Type head
     argument ends with a percent symbol ('%'), subdirectories are created
     for each process id.</p>
 
-    <p>This directive currently only works with the <module>prefork</module> 
+    <p>This directive currently only works with the <module>prefork</module>
     MPM.</p>
 </usage>
 </directivesynopsis>
@@ -1779,7 +1779,7 @@ wildcard matching available in 2.3.6 and
     <directive module="core">Include</directive> directive will fail with an
     error saying the file or directory cannot be found.</p>
 
-    <p>The file path specified may be an absolute path, or may be relative 
+    <p>The file path specified may be an absolute path, or may be relative
     to the <directive module="core">ServerRoot</directive> directory.</p>
 
     <p>Examples:</p>
@@ -1801,7 +1801,7 @@ wildcard matching available in 2.3.6 and
     path. In the following example, the server will fail to load if no
     directories match conf/vhosts/*, but will load successfully if no
     files match *.conf.</p>
-  
+
     <example>
       Include conf/vhosts/*/vhost.conf<br />
       Include conf/vhosts/*/*.conf
@@ -1813,7 +1813,7 @@ wildcard matching available in 2.3.6 and
     <example>
       Include strict conf/vhosts/*/*.conf
     </example>
-  
+
     <p>In this example, the server load successfully if either conf/vhosts/*
     matches no directories, or if *.conf matches no files:</p>
 
@@ -1825,7 +1825,7 @@ wildcard matching available in 2.3.6 and
 
 <seealso><program>apachectl</program></seealso>
 </directivesynopsis>
-  
+
 <directivesynopsis>
 <name>KeepAlive</name>
 <description>Enables HTTP persistent connections</description>
@@ -1872,7 +1872,7 @@ requests on a persistent connection</des
 <default>KeepAliveTimeout 5</default>
 <contextlist><context>server config</context><context>virtual host</context>
 </contextlist>
-<compatibility>Specifying a value in milliseconds is available in 
+<compatibility>Specifying a value in milliseconds is available in
 Apache httpd 2.3.2 and later</compatibility>
 
 <usage>
@@ -1886,7 +1886,7 @@ Apache httpd 2.3.2 and later</compatibil
     may cause performance problems in heavily loaded servers. The
     higher the timeout, the more server processes will be kept
     occupied waiting on connections with idle clients.</p>
-    
+
     <p>In a name-based virtual host context, the value of the first
     defined virtual host (the default host) in a set of <directive
     module="core">NameVirtualHost</directive> will be used.
@@ -1970,12 +1970,12 @@ methods</description>
       &lt;LimitExcept GET&gt;
       <indent>
         Require valid-user
-      </indent> 
+      </indent>
       &lt;/LimitExcept&gt;<br />
       &lt;Limit POST&gt;
       <indent>
         Require group editors
-      </indent> 
+      </indent>
       &lt;/Limit&gt;
     </example>
 </usage>
@@ -2092,8 +2092,8 @@ from the client</description>
     <example>
       LimitRequestBody 102400
     </example>
-    
-    <note><p>For a full description of how this directive is interpreted by 
+
+    <note><p>For a full description of how this directive is interpreted by
     proxy requests, see the <module>mod_proxy</module> documentation.</p>
     </note>
 
@@ -2139,7 +2139,7 @@ will be accepted from the client</descri
     </example>
 
      <note type="warning"><title>Warning</title>
-     <p> When name-based virtual hosting is used, the value for this 
+     <p> When name-based virtual hosting is used, the value for this
      directive is taken from the default (first-listed) virtual host for the
      <directive>NameVirtualHost</directive> the connection was mapped to.</p>
      </note>
@@ -2160,11 +2160,11 @@ client</description>
     that will be allowed in an HTTP request header.</p>
 
     <p>The <directive>LimitRequestFieldSize</directive> directive
-    allows the server administrator to reduce or increase the limit 
+    allows the server administrator to reduce or increase the limit
     on the allowed size of an HTTP request header field. A server
-    needs this value to be large enough to hold any one header field 
-    from a normal client request. The size of a normal request header 
-    field will vary greatly among different client implementations, 
+    needs this value to be large enough to hold any one header field
+    from a normal client request. The size of a normal request header
+    field will vary greatly among different client implementations,
     often depending upon the extent to which a user has configured
     their browser to support detailed content negotiation. SPNEGO
     authentication headers can be up to 12392 bytes.</p>
@@ -2183,7 +2183,7 @@ client</description>
     the default.</note>
 
     <note type="warning"><title>Warning</title>
-    <p> When name-based virtual hosting is used, the value for this 
+    <p> When name-based virtual hosting is used, the value for this
     directive is taken from the default (first-listed) virtual host for the
     <directive>NameVirtualHost</directive> the connection was mapped to.</p>
     </note>
@@ -2200,7 +2200,7 @@ from the client</description>
 <contextlist><context>server config</context><context>virtual host</context></contextlist>
 
 <usage>
-    <p>This directive sets the number of <var>bytes</var> that will be 
+    <p>This directive sets the number of <var>bytes</var> that will be
     allowed on the HTTP request-line.</p>
 
     <p>The <directive>LimitRequestLine</directive> directive allows
@@ -2227,7 +2227,7 @@ from the client</description>
     the default.</note>
 
     <note type="warning"><title>Warning</title>
-    <p> When name-based virtual hosting is used, the value for this 
+    <p> When name-based virtual hosting is used, the value for this
     directive is taken from the default (first-listed) virtual host for the
     <directive>NameVirtualHost</directive> the connection was mapped to.</p>
     </note>
@@ -2291,33 +2291,33 @@ URLs</description>
     <ul>
       <li>The specified location matches exactly the path component of the URL.
       </li>
-      <li>The specified location, which ends in a forward slash, is a prefix 
+      <li>The specified location, which ends in a forward slash, is a prefix
       of the path component of the URL (treated as a context root).
       </li>
-      <li>The specified location, with the addition of a trailing slash, is a 
+      <li>The specified location, with the addition of a trailing slash, is a
       prefix of the path component of the URL (also treated as a context root).
       </li>
     </ul>
     <p>
-    In the example below, where no trailing slash is used, requests to 
+    In the example below, where no trailing slash is used, requests to
     /private1, /private1/ and /private1/file.txt will have the enclosed
-    directives applied, but /private1other would not. 
+    directives applied, but /private1other would not.
     </p>
     <example>
       &lt;Location /private1&gt;
           ...
     </example>
     <p>
-    In the example below, where a trailing slash is used, requests to 
+    In the example below, where a trailing slash is used, requests to
     /private2/ and /private2/file.txt will have the enclosed
-    directives applied, but /private2 and /private2other would not. 
+    directives applied, but /private2 and /private2other would not.
     </p>
     <example>
       &lt;Location /private2<em>/</em>&gt;
           ...
     </example>
 
-    <note><title>When to use <directive 
+    <note><title>When to use <directive
     type="section">Location</directive></title>
 
     <p>Use <directive type="section">Location</directive> to apply
@@ -2325,7 +2325,7 @@ URLs</description>
     content that lives in the filesystem, use <directive
     type="section" module="core">Directory</directive> and <directive
     type="section" module="core">Files</directive>.  An exception is
-    <code>&lt;Location /&gt;</code>, which is an easy way to 
+    <code>&lt;Location /&gt;</code>, which is an easy way to
     apply a configuration to the entire server.</p>
     </note>
 
@@ -2341,7 +2341,7 @@ URLs</description>
     characters. Neither wildcard character matches a / in the URL-path.</p>
 
     <p><glossary ref="regex">Regular expressions</glossary>
-    can also be used, with the addition of the <code>~</code> 
+    can also be used, with the addition of the <code>~</code>
     character. For example:</p>
 
     <example>
@@ -2705,7 +2705,7 @@ or specified mutexes</description>
         <li><code>default | yes</code>
         <p>This selects the default locking implementation, as determined by
         <glossary>APR</glossary>.  The default locking implementation can
-        be displayed by running <program>httpd</program> with the 
+        be displayed by running <program>httpd</program> with the
         <code>-V</code> option.</p></li>
 
         <li><code>none | no</code>
@@ -2726,7 +2726,7 @@ or specified mutexes</description>
         <p>This is a mutex variant based on a SystemV IPC semaphore.</p>
 
         <note type="warning"><title>Warning</title>
-        <p>It is possible to "leak" SysV semaphores if processes crash 
+        <p>It is possible to "leak" SysV semaphores if processes crash
         before the semaphore is removed.</p>
 	</note>
 
@@ -2761,7 +2761,7 @@ or specified mutexes</description>
         </li>
 
         <li><code>fcntl:/path/to/mutex</code>
-        <p>This is a mutex variant where a physical (lock-)file and the 
+        <p>This is a mutex variant where a physical (lock-)file and the
         <code>fcntl()</code> function are used as the mutex.</p>
 
         <note type="warning"><title>Warning</title>
@@ -2783,10 +2783,10 @@ or specified mutexes</description>
         order.</p></li>
     </ul>
 
-    <p>Most mechanisms are only available on selected platforms, where the 
+    <p>Most mechanisms are only available on selected platforms, where the
     underlying platform and <glossary>APR</glossary> support it.  Mechanisms
     which aren't available on all platforms are <em>posixsem</em>,
-    <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>, 
+    <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>,
     <em>flock</em>, and <em>file</em>.</p>
 
     <p>With the file-based mechanisms <em>fcntl</em> and <em>flock</em>,
@@ -2796,12 +2796,12 @@ or specified mutexes</description>
     filesystem for <code>/path/to/mutex</code> and never a directory residing
     on a NFS- or AFS-filesystem.  The basename of the file will be the mutex
     type, an optional instance string provided by the module, and unless the
-    <code>OmitPID</code> keyword is specified, the process id of the httpd 
+    <code>OmitPID</code> keyword is specified, the process id of the httpd
     parent process will be appended to to make the file name unique, avoiding
     conflicts when multiple httpd instances share a lock file directory.  For
     example, if the mutex name is <code>mpm-accept</code> and the lock file
     directory is <code>/var/httpd/locks</code>, the lock file name for the
-    httpd instance with parent process id 12345 would be 
+    httpd instance with parent process id 12345 would be
     <code>/var/httpd/locks/mpm-accept.12345</code>.</p>
 
     <note type="warning"><title>Security</title>
@@ -2892,15 +2892,15 @@ hosting</description>
 
 <usage>
 
-<p>A single <directive>NameVirtualHost</directive> directive 
-identifies a set of identical virtual hosts on which the server will  
-further select from on the basis of the <em>hostname</em> 
+<p>A single <directive>NameVirtualHost</directive> directive
+identifies a set of identical virtual hosts on which the server will
+further select from on the basis of the <em>hostname</em>
 requested by the client.  The <directive>NameVirtualHost</directive>
-directive is a required directive if you want to configure 
+directive is a required directive if you want to configure
 <a href="../vhosts/">name-based virtual hosts</a>.</p>
 
 <p>This directive, and the corresponding <directive >VirtualHost</directive>,
-<em>must</em> be qualified with a port number if the server supports both HTTP 
+<em>must</em> be qualified with a port number if the server supports both HTTP
 and HTTPS connections.</p>
 
 <p>Although <var>addr</var> can be a hostname, it is recommended
@@ -2908,16 +2908,16 @@ that you always use an IP address or a w
 NameVirtualHost matches only virtualhosts that also have a literal wildcard
 as their argument.</p>
 
-<p>In cases where a firewall or other proxy receives the requests and 
+<p>In cases where a firewall or other proxy receives the requests and
 forwards them on a different IP address to the server, you must specify the
 IP address of the physical interface on the machine which will be
 servicing the requests. </p>
 
-<p> In the example below, requests received on interface 192.0.2.1 and port 80 
+<p> In the example below, requests received on interface 192.0.2.1 and port 80
 will only select among the first two virtual hosts. Requests received on
 port 80 on any other interface will only select among the third and fourth
-virtual hosts. In the common case where the interface isn't important 
-to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives 
+virtual hosts. In the common case where the interface isn't important
+to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives
 are necessary.</p>
 
    <example>
@@ -3355,7 +3355,7 @@ of a request or the last 63, assuming th
 
 <usage>
     <p>mod_status with <code>ExtendedStatus On</code>
-    displays the actual request being handled. 
+    displays the actual request being handled.
     For historical purposes, only 63 characters of the request
     are actually stored for display purposes. This directive
     controls whether the 1st 63 characters are stored (the previous
@@ -3457,7 +3457,7 @@ itself</description>
     in conjunction with <directive>ServerAlias</directive>) to uniquely
     identify a virtual host, when using <a
     href="../vhosts/name-based.html">name-based virtual hosts</a>.</p>
-    
+
     <p>For example, if the name of the
     machine hosting the web server is <code>simple.example.com</code>,
     but the machine also has the DNS alias <code>www.example.com</code>
@@ -3465,7 +3465,7 @@ itself</description>
     directive should be used:</p>
 
     <example>
-      ServerName www.example.com:80
+      ServerName www.example.com
     </example>
 
     <p>The <directive>ServerName</directive> directive
@@ -3494,7 +3494,7 @@ itself</description>
     <code>https://</code> scheme and the port number to which the
     clients connect in the <directive>ServerName</directive> directive
     to make sure that the server generates the correct
-    self-referential URLs. 
+    self-referential URLs.
     </p>
 
     <p>See the description of the
@@ -3556,7 +3556,7 @@ is accessed by an incompatible browser</
     subdirectories <code>conf/</code> and <code>logs/</code>. Relative
     paths in other configuration directives (such as <directive
     module="core">Include</directive> or <directive
-    module="mod_so">LoadModule</directive>, for example) are taken as 
+    module="mod_so">LoadModule</directive>, for example) are taken as
     relative to this directory.</p>
 
     <example><title>Example</title>
@@ -3661,7 +3661,7 @@ header</description>
     <p>After version 2.0.44, this directive also controls the
     information presented by the <directive
     module="core">ServerSignature</directive> directive.</p>
-    
+
     <note>Setting <directive>ServerTokens</directive> to less than
     <code>minimal</code> is not recommended because it makes it more
     difficult to debug interoperational problems. Also note that
@@ -3838,7 +3838,7 @@ certain events before failing a request<
     allowed) error to the client.</p>
 
     <p>Finally, for testing and diagnostic purposes only, request
-    bodies may be allowed using the non-compliant <code>TraceEnable 
+    bodies may be allowed using the non-compliant <code>TraceEnable
     extended</code> directive.  The core (as an origin server) will
     restrict the request body to 64k (plus 8k for chunk headers if
     <code>Transfer-Encoding: chunked</code> is used).  The core will
@@ -3960,7 +3960,7 @@ port</description>
       <li>Port provided in <code>Servername</code></li>
       <li>Default port</li>
      </ul>
-    
+
     <p>With <code>UseCanonicalPhysicalPort Off</code>, the
     physical ports are removed from the ordering.</p>
     </note>



Mime
View raw message