Simply remove trailing whitespace.

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

1 files changed, 13 insertions, 13 deletions

diff --git a/docs/manual/caching.xml b/docs/manual/caching.xml
index f08ed7a77f..9a7112e5d5 100644
--- a/docs/manual/caching.xml
+++ b/docs/manual/caching.xml
@@ -34,7 +34,7 @@
 
   <section id="introduction">
     <title>Introduction</title>
-    
+
     <p>The Apache HTTP server offers a range of caching features that
     are designed to improve the performance of the server in various
     ways.</p>
@@ -104,7 +104,7 @@
     </related>
 
     <p>The HTTP protocol contains built in support for an in-line caching
-    mechanism 
+    mechanism
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html">
     described by section 13 of RFC2616</a>, and the
     <module>mod_cache</module> module can be used to take advantage of
@@ -180,14 +180,14 @@
 
               <p>In this scenario, the cache behaves as if it has been "bolted
               on" to the front of the server.</p>
-              
+
               <p>This mode offers the best performance, as the majority of
               server processing is bypassed. This mode however also bypasses the
               authentication and authorization phases of server processing, so
               this mode should be chosen with care when this is important.</p>
-  
+
               <p> Requests with an "Authorization" header (for example, HTTP Basic
-              Authentication) are neither cacheable nor served from the cache 
+              Authentication) are neither cacheable nor served from the cache
               when <module>mod_cache</module> is running in this phase.</p>
           </dd>
           <dt>Normal handler phase</dt>
@@ -242,7 +242,7 @@
       explicit freshness lifetime with the <code>Cache-Control</code>
       header's <code>max-age</code> or <code>s-maxage</code> fields, or
       by including an <code>Expires</code> header.</p>
-      
+
       <p>At the same time, the origin server defined freshness lifetime can
       be overridden by a client when the client presents their own
       <code>Cache-Control</code> header within the request. In this case,
@@ -309,7 +309,7 @@
       see if the file has changed in size or modification time. As such, even
       local content may still be served faster from the cache if it has not
       changed.</p>
-      
+
       <p>Origin servers should make every effort to support conditional
       requests as is practical, however if conditional requests are not
       supported, the origin will respond as if the request was not
@@ -384,7 +384,7 @@
       particulars of the request that are not covered by HTTP negotiation,
       should not be cached. This content should declare itself uncacheable
       using the <code>Cache-Control</code> header.</p>
-      
+
       <p>If content changes often, expressed by a freshness lifetime of minutes
       or seconds, the content can still be cached, however it is highly
       desirable that the origin server supports
@@ -404,7 +404,7 @@
       based on the value of headers in the request, for example to serve
       multiple languages at the same URL, HTTP's caching mechanism makes it
       possible to cache multiple variants of the same page at the same URL.</p>
-      
+
       <p>This is done by the origin server adding a <code>Vary</code> header
       to indicate which headers must be taken into account by a cache when
       determining whether two variants are different from one another.</p>
@@ -418,7 +418,7 @@ Vary: negotiate,accept-language,accept-charset
       <p><module>mod_cache</module> will only serve the cached content to
       requesters with accept-language and accept-charset headers
       matching those of the original request.</p>
-      
+
       <p>Multiple variants of the content can be cached side by side,
       <module>mod_cache</module> uses the <code>Vary</code> header and the
       corresponding values of the request headers listed by <code>Vary</code>
@@ -527,7 +527,7 @@ CacheDirLength 1
       or more to process very large (tens of gigabytes) caches and if you are
       running it from cron it is recommended that you determine how long a typical
       run takes, to avoid running more than one instance at a time.</p>
- 
+
       <p>It is also recommended that an appropriate "nice" level is chosen for
       htcacheclean so that the tool does not cause excessive disk io while the
       server is running.</p>
@@ -565,7 +565,7 @@ CacheDirLength 1
           <directive module="mod_ssl">SSLStaplingCache</directive>
         </directivelist>
     </related>
-    
+
     <p>The Apache HTTP server offers a low level shared object cache for
     caching information such as SSL sessions, or authentication credentials,
     within the <a href="socache.html">socache</a> interface.</p>
@@ -872,7 +872,7 @@ sys     0m0.000s</pre>
       on the popularity of the particular web site thousands or millions of
       duplicate cache entries could be created for the same URL, crowding
       out other entries in the cache.</p>
-      
+
       <p>In other cases, there may be a need to change the URL of a particular
       resource on every request, usually by adding a "cachebuster" string to
       the URL. If this content is declared cacheable by a server for a