httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject svn commit: r1673947 [1/6] - in /httpd/httpd/trunk/docs/manual: ./ developer/ howto/ mod/ platform/ programs/ rewrite/ ssl/ vhosts/
Date Wed, 15 Apr 2015 20:16:26 GMT
Author: coar
Date: Wed Apr 15 20:16:24 2015
New Revision: 1673947

URL: http://svn.apache.org/r1673947
Log:
Simply remove trailing whitespace.

Modified:
    httpd/httpd/trunk/docs/manual/bind.xml
    httpd/httpd/trunk/docs/manual/caching.html.en
    httpd/httpd/trunk/docs/manual/caching.xml
    httpd/httpd/trunk/docs/manual/compliance.html.en
    httpd/httpd/trunk/docs/manual/compliance.xml
    httpd/httpd/trunk/docs/manual/configuring.html.en
    httpd/httpd/trunk/docs/manual/configuring.xml
    httpd/httpd/trunk/docs/manual/developer/hooks.html.en
    httpd/httpd/trunk/docs/manual/developer/hooks.xml
    httpd/httpd/trunk/docs/manual/developer/modguide.html.en
    httpd/httpd/trunk/docs/manual/developer/modguide.xml
    httpd/httpd/trunk/docs/manual/developer/new_api_2_4.html.en
    httpd/httpd/trunk/docs/manual/developer/new_api_2_4.xml
    httpd/httpd/trunk/docs/manual/developer/output-filters.html.en
    httpd/httpd/trunk/docs/manual/developer/output-filters.xml
    httpd/httpd/trunk/docs/manual/developer/request.html.en
    httpd/httpd/trunk/docs/manual/developer/request.xml
    httpd/httpd/trunk/docs/manual/env.xml.ja
    httpd/httpd/trunk/docs/manual/env.xml.ko
    httpd/httpd/trunk/docs/manual/env.xml.tr
    httpd/httpd/trunk/docs/manual/expr.xml.fr
    httpd/httpd/trunk/docs/manual/glossary.html.en
    httpd/httpd/trunk/docs/manual/glossary.xml
    httpd/httpd/trunk/docs/manual/handler.xml.es
    httpd/httpd/trunk/docs/manual/handler.xml.fr
    httpd/httpd/trunk/docs/manual/handler.xml.ja
    httpd/httpd/trunk/docs/manual/handler.xml.ko
    httpd/httpd/trunk/docs/manual/handler.xml.tr
    httpd/httpd/trunk/docs/manual/handler.xml.zh-cn
    httpd/httpd/trunk/docs/manual/howto/access.xml.fr
    httpd/httpd/trunk/docs/manual/howto/cgi.xml.fr
    httpd/httpd/trunk/docs/manual/howto/cgi.xml.ja
    httpd/httpd/trunk/docs/manual/howto/cgi.xml.ko
    httpd/httpd/trunk/docs/manual/howto/ssi.html.en
    httpd/httpd/trunk/docs/manual/howto/ssi.xml
    httpd/httpd/trunk/docs/manual/install.html.en
    httpd/httpd/trunk/docs/manual/install.xml
    httpd/httpd/trunk/docs/manual/mod/index.html.de
    httpd/httpd/trunk/docs/manual/mod/index.html.en
    httpd/httpd/trunk/docs/manual/mod/index.html.es
    httpd/httpd/trunk/docs/manual/mod/index.html.fr
    httpd/httpd/trunk/docs/manual/mod/index.html.ja.utf8
    httpd/httpd/trunk/docs/manual/mod/index.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/mod/index.html.tr.utf8
    httpd/httpd/trunk/docs/manual/mod/index.html.zh-cn.utf8
    httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_alias.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_alias.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_alias.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_alias.xml.tr
    httpd/httpd/trunk/docs/manual/mod/mod_allowmethods.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_auth_digest.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_auth_digest.xml
    httpd/httpd/trunk/docs/manual/mod/mod_authn_anon.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_authn_anon.xml
    httpd/httpd/trunk/docs/manual/mod/mod_authn_core.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_authn_core.xml
    httpd/httpd/trunk/docs/manual/mod/mod_authn_socache.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_authz_core.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_authz_core.xml
    httpd/httpd/trunk/docs/manual/mod/mod_autoindex.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_autoindex.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_autoindex.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_autoindex.xml.tr
    httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_cache.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_cgid.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_cgid.html.ja.utf8
    httpd/httpd/trunk/docs/manual/mod/mod_cgid.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/mod/mod_cgid.xml
    httpd/httpd/trunk/docs/manual/mod/mod_dbd.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_dbd.xml
    httpd/httpd/trunk/docs/manual/mod/mod_deflate.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_deflate.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_deflate.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_dialup.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_dir.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_dir.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_dir.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_dir.xml.tr
    httpd/httpd/trunk/docs/manual/mod/mod_env.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_env.xml
    httpd/httpd/trunk/docs/manual/mod/mod_ext_filter.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_ext_filter.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_ext_filter.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_firehose.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_firehose.xml
    httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_headers.xml
    httpd/httpd/trunk/docs/manual/mod/mod_heartbeat.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_heartbeat.xml
    httpd/httpd/trunk/docs/manual/mod/mod_heartmonitor.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_heartmonitor.xml
    httpd/httpd/trunk/docs/manual/mod/mod_include.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_include.xml
    httpd/httpd/trunk/docs/manual/mod/mod_lbmethod_heartbeat.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_lbmethod_heartbeat.xml
    httpd/httpd/trunk/docs/manual/mod/mod_ldap.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_log_config.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_log_config.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_log_config.xml.tr
    httpd/httpd/trunk/docs/manual/mod/mod_log_forensic.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_log_forensic.xml
    httpd/httpd/trunk/docs/manual/mod/mod_logio.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_logio.xml
    httpd/httpd/trunk/docs/manual/mod/mod_lua.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_macro.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_sed.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_sed.xml
    httpd/httpd/trunk/docs/manual/mod/mod_session.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_session.xml
    httpd/httpd/trunk/docs/manual/mod/mod_setenvif.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml
    httpd/httpd/trunk/docs/manual/mod/mod_slotmem_plain.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_slotmem_plain.xml
    httpd/httpd/trunk/docs/manual/mod/mod_socache_dbm.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_socache_dbm.xml
    httpd/httpd/trunk/docs/manual/mod/mod_socache_memcache.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_socache_memcache.xml
    httpd/httpd/trunk/docs/manual/mod/mod_socache_shmcb.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_socache_shmcb.xml
    httpd/httpd/trunk/docs/manual/mod/mod_ssl_ct.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_ssl_ct.xml
    httpd/httpd/trunk/docs/manual/mod/mod_status.xml.fr
    httpd/httpd/trunk/docs/manual/mod/mod_status.xml.ja
    httpd/httpd/trunk/docs/manual/mod/mod_status.xml.ko
    httpd/httpd/trunk/docs/manual/mod/mod_status.xml.tr
    httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.xml.tr
    httpd/httpd/trunk/docs/manual/mod/mod_watchdog.html.en
    httpd/httpd/trunk/docs/manual/mod/mod_watchdog.xml
    httpd/httpd/trunk/docs/manual/mod/mpm_common.html.en
    httpd/httpd/trunk/docs/manual/mod/mpm_common.xml
    httpd/httpd/trunk/docs/manual/mod/mpm_winnt.html.en
    httpd/httpd/trunk/docs/manual/mod/mpm_winnt.xml
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.de
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.en
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.es
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.ja.utf8
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.tr.utf8
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.zh-cn.utf8
    httpd/httpd/trunk/docs/manual/new_features_2_4.html.en
    httpd/httpd/trunk/docs/manual/new_features_2_4.xml
    httpd/httpd/trunk/docs/manual/platform/rpm.html.en
    httpd/httpd/trunk/docs/manual/platform/rpm.xml
    httpd/httpd/trunk/docs/manual/platform/win_compiling.html.en
    httpd/httpd/trunk/docs/manual/platform/win_compiling.xml
    httpd/httpd/trunk/docs/manual/platform/windows.xml.ko
    httpd/httpd/trunk/docs/manual/programs/ab.html.en
    httpd/httpd/trunk/docs/manual/programs/ab.xml
    httpd/httpd/trunk/docs/manual/programs/configure.xml
    httpd/httpd/trunk/docs/manual/programs/htdigest.html.en
    httpd/httpd/trunk/docs/manual/programs/htdigest.xml
    httpd/httpd/trunk/docs/manual/programs/httxt2dbm.html.en
    httpd/httpd/trunk/docs/manual/programs/httxt2dbm.xml
    httpd/httpd/trunk/docs/manual/rewrite/flags.xml.fr
    httpd/httpd/trunk/docs/manual/rewrite/index.html.fr
    httpd/httpd/trunk/docs/manual/rewrite/index.xml.fr
    httpd/httpd/trunk/docs/manual/rewrite/index.xml.meta
    httpd/httpd/trunk/docs/manual/rewrite/index.xml.tr
    httpd/httpd/trunk/docs/manual/rewrite/index.xml.zh-cn
    httpd/httpd/trunk/docs/manual/rewrite/intro.html.fr
    httpd/httpd/trunk/docs/manual/rewrite/intro.xml.fr
    httpd/httpd/trunk/docs/manual/rewrite/intro.xml.meta
    httpd/httpd/trunk/docs/manual/rewrite/tech.html.fr
    httpd/httpd/trunk/docs/manual/rewrite/tech.xml.fr
    httpd/httpd/trunk/docs/manual/rewrite/tech.xml.meta
    httpd/httpd/trunk/docs/manual/sections.xml.fr
    httpd/httpd/trunk/docs/manual/sections.xml.ja
    httpd/httpd/trunk/docs/manual/sections.xml.ko
    httpd/httpd/trunk/docs/manual/sections.xml.tr
    httpd/httpd/trunk/docs/manual/ssl/ssl_faq.html.fr
    httpd/httpd/trunk/docs/manual/ssl/ssl_faq.xml.fr
    httpd/httpd/trunk/docs/manual/ssl/ssl_faq.xml.meta
    httpd/httpd/trunk/docs/manual/ssl/ssl_howto.xml.fr
    httpd/httpd/trunk/docs/manual/suexec.html.fr
    httpd/httpd/trunk/docs/manual/suexec.xml.fr
    httpd/httpd/trunk/docs/manual/suexec.xml.ja
    httpd/httpd/trunk/docs/manual/suexec.xml.ko
    httpd/httpd/trunk/docs/manual/suexec.xml.meta
    httpd/httpd/trunk/docs/manual/suexec.xml.tr
    httpd/httpd/trunk/docs/manual/upgrading.html.en
    httpd/httpd/trunk/docs/manual/upgrading.xml
    httpd/httpd/trunk/docs/manual/urlmapping.xml.fr
    httpd/httpd/trunk/docs/manual/urlmapping.xml.ja
    httpd/httpd/trunk/docs/manual/urlmapping.xml.ko
    httpd/httpd/trunk/docs/manual/urlmapping.xml.tr
    httpd/httpd/trunk/docs/manual/vhosts/details.html.en
    httpd/httpd/trunk/docs/manual/vhosts/details.xml
    httpd/httpd/trunk/docs/manual/vhosts/examples.xml.fr
    httpd/httpd/trunk/docs/manual/vhosts/examples.xml.ja
    httpd/httpd/trunk/docs/manual/vhosts/examples.xml.ko
    httpd/httpd/trunk/docs/manual/vhosts/examples.xml.tr
    httpd/httpd/trunk/docs/manual/vhosts/mass.xml.fr
    httpd/httpd/trunk/docs/manual/vhosts/mass.xml.ko
    httpd/httpd/trunk/docs/manual/vhosts/mass.xml.tr
    httpd/httpd/trunk/docs/manual/vhosts/name-based.xml.de
    httpd/httpd/trunk/docs/manual/vhosts/name-based.xml.fr
    httpd/httpd/trunk/docs/manual/vhosts/name-based.xml.ja
    httpd/httpd/trunk/docs/manual/vhosts/name-based.xml.ko
    httpd/httpd/trunk/docs/manual/vhosts/name-based.xml.tr

Modified: httpd/httpd/trunk/docs/manual/bind.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/bind.xml?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/bind.xml (original)
+++ httpd/httpd/trunk/docs/manual/bind.xml Wed Apr 15 20:16:24 2015
@@ -105,7 +105,7 @@ Listen 192.0.2.5:8000
       (48)Address already in use: make_sock: could not bind to address [::]:80
     </example>
 
-    <p>See <a 
+    <p>See <a
     href="http://wiki.apache.org/httpd/CouldNotBindToAddress">the
     discussion in the wiki</a> for further troubleshooting tips.</p>
 
@@ -205,4 +205,3 @@ Listen 192.0.2.1:80
     server is not listening to, it cannot be accessed.</p>
   </section>
 </manualpage>
-

Modified: httpd/httpd/trunk/docs/manual/caching.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/caching.html.en?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/caching.html.en (original)
+++ httpd/httpd/trunk/docs/manual/caching.html.en Wed Apr 15 20:16:24 2015
@@ -41,7 +41,7 @@
 <div class="section">
 <h2><a name="introduction" id="introduction">Introduction</a></h2>
     
-    
+
     <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>
@@ -100,7 +100,7 @@
     <table class="related"><tr><th>Related Modules</th><th>Related
Directives</th></tr><tr><td><ul><li><code class="module"><a
href="./mod/mod_cache.html">mod_cache</a></code></li><li><code
class="module"><a href="./mod/mod_cache_disk.html">mod_cache_disk</a></code></li></ul></td><td><ul><li><code
class="directive"><a href="./mod/mod_cache.html#cacheenable">CacheEnable</a></code></li><li><code
class="directive"><a href="./mod/mod_cache.html#cachedisable">CacheDisable</a></code></li><li><code
class="directive"><a href="./mod/core.html#usecanonicalname">UseCanonicalName</a></code></li><li><code
class="directive"><a href="./mod/mod_negotiation.html#cachenegotiateddocs">CacheNegotiatedDocs</a></code></li></ul></td></tr></table>
 
     <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
     <code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>
module can be used to take advantage of
@@ -175,14 +175,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 <code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>
is running in this phase.</p>
           </dd>
           <dt>Normal handler phase</dt>
@@ -237,7 +237,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,
@@ -302,7 +302,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
@@ -375,7 +375,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
@@ -395,7 +395,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>
@@ -409,7 +409,7 @@ Vary: negotiate,accept-language,accept-c
       <p><code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>
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,
       <code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>
uses the <code>Vary</code> header and the
       corresponding values of the request headers listed by <code>Vary</code>
@@ -514,7 +514,7 @@ CacheDirLength 1</pre>
       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>
@@ -537,7 +537,7 @@ CacheDirLength 1</pre>
     
 
     <table class="related"><tr><th>Related Modules</th><th>Related
Directives</th></tr><tr><td><ul><li><code class="module"><a
href="./mod/mod_authn_socache.html">mod_authn_socache</a></code></li><li><code
class="module"><a href="./mod/mod_socache_dbm.html">mod_socache_dbm</a></code></li><li><code
class="module"><a href="./mod/mod_socache_dc.html">mod_socache_dc</a></code></li><li><code
class="module"><a href="./mod/mod_socache_memcache.html">mod_socache_memcache</a></code></li><li><code
class="module"><a href="./mod/mod_socache_shmcb.html">mod_socache_shmcb</a></code></li><li><code
class="module"><a href="./mod/mod_ssl.html">mod_ssl</a></code></li></ul></td><td><ul><li><code
class="directive"><a href="./mod/mod_authn_socache.html#authncachesocache">AuthnCacheSOCache</a></code></li><li><code
class="directive"><a href="./mod/mod_ssl.html#sslsessioncache">SSLSessionCache</a></code></li><li><code
class="directive"><a href="./mod/mod_ssl.html#sslstaplingcache">SSLStaplingCache</a></code
 ></li></ul></td></tr></table>
-    
+
     <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>
@@ -816,7 +816,7 @@ sys     0m0.000s</pre></div>
       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

Modified: httpd/httpd/trunk/docs/manual/caching.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/caching.xml?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/caching.xml (original)
+++ httpd/httpd/trunk/docs/manual/caching.xml Wed Apr 15 20:16:24 2015
@@ -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-c
       <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

Modified: httpd/httpd/trunk/docs/manual/compliance.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/compliance.html.en?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/compliance.html.en (original)
+++ httpd/httpd/trunk/docs/manual/compliance.html.en Wed Apr 15 20:16:24 2015
@@ -179,12 +179,12 @@
 
     <p>This policy will be rejected if the server response does not contain
     an explicit <code>Content-Length</code> header.</p>
-    
+
     <p>There are a number of ways of determining the length of a response
     body, described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
-    
+
     <p>When the <code>Content-Length</code> header is present, the size
of
     the body is declared at the start of the response. If this information
     is missing, an HTTP cache might choose to ignore the response, as it
@@ -231,9 +231,9 @@
     header, and the format of the header is described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7">
     RFC2616 section 3.7 Media Types</a>.</p>
-    
+
     <p>A syntactically valid content type might look as follows:</p>
-    
+
     <div class="example"><p><code>
       Content-Type: text/html; charset=iso-8859-1
     </code></p></div>
@@ -244,7 +244,7 @@
       # invalid<br />
       Content-Type: foo<br />
       # blank<br />
-      Content-Type: 
+      Content-Type:
     </code></p></div>
 
     <p>The server administrator has the option to restrict the policy to one
@@ -263,12 +263,12 @@
     <p>This policy will be rejected if the server response does not contain
     an explicit <code>Content-Length</code> header, or a
     <code>Transfer-Encoding</code> of chunked.</p>
-    
+
     <p>There are a number of ways of determining the length of a response
     body, described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
-    
+
     <p>When the <code>Content-Length</code> header is present, the size
of
     the body is declared at the start of the response. HTTP/1.1 defines the
     <code>Transfer-Encoding</code> header as an alternative to
@@ -281,33 +281,33 @@
     </p>
 
     <p>Most specifically, we follow these rules:</p>
-    
+
     <dl>
     <dt>IF</dt>
     <dd>we have not marked this connection as errored;</dd>
-    
+
     <dt>and</dt>
     <dd>the client isn't expecting 100-continue</dd>
-    
+
     <dt>and</dt>
     <dd>the response status does not require a close;</dd>
-    
+
     <dt>and</dt>
     <dd>the response body has a defined length due to the status code
     being 304 or 204, the request method being HEAD, already having defined
     Content-Length or Transfer-Encoding: chunked, or the request version
     being HTTP/1.1 and thus capable of being set as chunked</dd>
-    
+
     <dt>THEN</dt>
     <dd>we support keepalive.</dd>
     </dl>
-   
+
     <div class="warning">The server may choose to turn off keepalive for
     various reasons, such as an imminent shutdown, or a Connection: close from
     the client, or an HTTP/1.0 client request with a response with no
     <code>Content-Length</code>, but for our purposes we only care that
     keepalive was possible from the application, not that keepalive actually
-    took place.</div> 
+    took place.</div>
 
     <p>It should also be noted that the Apache httpd server includes a filter
     that adds chunked encoding to responses without an explicit content
@@ -316,7 +316,7 @@
 
     <p>This policy is implemented by the <strong>POLICY_KEEPALIVE</strong>
     filter.</p>
-    
+
   </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif"
/></a></div>
 <div class="section">
 <h2><a name="policymaxage" id="policymaxage">Freshness Lifetime / Maxage Policy</a></h2>
@@ -418,7 +418,7 @@
 <h2><a name="policyvary" id="policyvary">Vary Header Policy</a></h2>
     
     <table class="related"><tr><th>Related Modules</th><th>Related
Directives</th></tr><tr><td><ul><li><code class="module"><a
href="./mod/mod_policy.html">mod_policy</a></code></li></ul></td><td><ul><li><code
class="directive"><a href="./mod/mod_policy.html#policyvary">PolicyVary</a></code></li></ul></td></tr></table>
-    
+
     <p>This policy will be rejected if the server response contains a
     <code>Vary</code> header, and that header in turn contains a header
     blacklisted by the administrator.</p>
@@ -426,7 +426,7 @@
     <p>The <code>Vary</code> header is described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.44">
     RFC2616 section 14.44 Vary</a>.</p>
-    
+
     <p>Some client provided headers, such as <code>User-Agent</code>,
     can contain thousands or millions of combinations of values over a period
     of time, and if the response is declared cacheable, a cache might attempt

Modified: httpd/httpd/trunk/docs/manual/compliance.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/compliance.xml?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/compliance.xml (original)
+++ httpd/httpd/trunk/docs/manual/compliance.xml Wed Apr 15 20:16:24 2015
@@ -199,12 +199,12 @@
 
     <p>This policy will be rejected if the server response does not contain
     an explicit <code>Content-Length</code> header.</p>
-    
+
     <p>There are a number of ways of determining the length of a response
     body, described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
-    
+
     <p>When the <code>Content-Length</code> header is present, the size
of
     the body is declared at the start of the response. If this information
     is missing, an HTTP cache might choose to ignore the response, as it
@@ -258,9 +258,9 @@
     header, and the format of the header is described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7">
     RFC2616 section 3.7 Media Types</a>.</p>
-    
+
     <p>A syntactically valid content type might look as follows:</p>
-    
+
     <example>
       Content-Type: text/html; charset=iso-8859-1
     </example>
@@ -271,7 +271,7 @@
       # invalid<br />
       Content-Type: foo<br />
       # blank<br />
-      Content-Type: 
+      Content-Type:
     </example>
 
     <p>The server administrator has the option to restrict the policy to one
@@ -297,12 +297,12 @@
     <p>This policy will be rejected if the server response does not contain
     an explicit <code>Content-Length</code> header, or a
     <code>Transfer-Encoding</code> of chunked.</p>
-    
+
     <p>There are a number of ways of determining the length of a response
     body, described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
-    
+
     <p>When the <code>Content-Length</code> header is present, the size
of
     the body is declared at the start of the response. HTTP/1.1 defines the
     <code>Transfer-Encoding</code> header as an alternative to
@@ -315,33 +315,33 @@
     </p>
 
     <p>Most specifically, we follow these rules:</p>
-    
+
     <dl>
     <dt>IF</dt>
     <dd>we have not marked this connection as errored;</dd>
-    
+
     <dt>and</dt>
     <dd>the client isn't expecting 100-continue</dd>
-    
+
     <dt>and</dt>
     <dd>the response status does not require a close;</dd>
-    
+
     <dt>and</dt>
     <dd>the response body has a defined length due to the status code
     being 304 or 204, the request method being HEAD, already having defined
     Content-Length or Transfer-Encoding: chunked, or the request version
     being HTTP/1.1 and thus capable of being set as chunked</dd>
-    
+
     <dt>THEN</dt>
     <dd>we support keepalive.</dd>
     </dl>
-   
+
     <note type="warning">The server may choose to turn off keepalive for
     various reasons, such as an imminent shutdown, or a Connection: close from
     the client, or an HTTP/1.0 client request with a response with no
     <code>Content-Length</code>, but for our purposes we only care that
     keepalive was possible from the application, not that keepalive actually
-    took place.</note> 
+    took place.</note>
 
     <p>It should also be noted that the Apache httpd server includes a filter
     that adds chunked encoding to responses without an explicit content
@@ -350,7 +350,7 @@
 
     <p>This policy is implemented by the <strong>POLICY_KEEPALIVE</strong>
     filter.</p>
-    
+
   </section>
 
   <section id="policymaxage">
@@ -392,7 +392,7 @@
     filter.</p>
 
   </section>
-  
+
   <section id="policynocache">
     <title>No Cache Policy</title>
     <related>
@@ -434,7 +434,7 @@
     filter.</p>
 
   </section>
-  
+
   <section id="policyvalidation">
     <title>Validation Policy</title>
     <related>
@@ -469,7 +469,7 @@
     filter.</p>
 
   </section>
-  
+
   <section id="policyvary">
     <title>Vary Header Policy</title>
     <related>
@@ -480,7 +480,7 @@
         <directive module="mod_policy">PolicyVary</directive>
       </directivelist>
     </related>
-    
+
     <p>This policy will be rejected if the server response contains a
     <code>Vary</code> header, and that header in turn contains a header
     blacklisted by the administrator.</p>
@@ -488,7 +488,7 @@
     <p>The <code>Vary</code> header is described in full in
     <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.44">
     RFC2616 section 14.44 Vary</a>.</p>
-    
+
     <p>Some client provided headers, such as <code>User-Agent</code>,
     can contain thousands or millions of combinations of values over a period
     of time, and if the response is declared cacheable, a cache might attempt
@@ -500,7 +500,7 @@
     filter.</p>
 
   </section>
-  
+
   <section id="policyversion">
     <title>Protocol Version Policy</title>
     <related>

Modified: httpd/httpd/trunk/docs/manual/configuring.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/configuring.html.en?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/configuring.html.en (original)
+++ httpd/httpd/trunk/docs/manual/configuring.html.en Wed Apr 15 20:16:24 2015
@@ -69,14 +69,14 @@ Server.</p>
     There must be no other characters or white space between the
     backslash and the end of the line.</p>
 
-    <p>Arguments to directives are separated by whitespace. If an 
+    <p>Arguments to directives are separated by whitespace. If an
     argument contains spaces, you must enclose that argument in quotes.</p>
 
     <p>Directives in the configuration files are case-insensitive,
     but arguments to directives are often case sensitive. Lines
     that begin with the hash character "#" are considered
     comments, and are ignored. Comments may <strong>not</strong> be
-    included on the same line as a configuration directive. 
+    included on the same line as a configuration directive.
     White space occurring before a directive is ignored, so
     you may indent directives for clarity. Blank lines are also ignored.</p>
 

Modified: httpd/httpd/trunk/docs/manual/configuring.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/configuring.xml?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/configuring.xml (original)
+++ httpd/httpd/trunk/docs/manual/configuring.xml Wed Apr 15 20:16:24 2015
@@ -69,14 +69,14 @@ Server.</p>
     There must be no other characters or white space between the
     backslash and the end of the line.</p>
 
-    <p>Arguments to directives are separated by whitespace. If an 
+    <p>Arguments to directives are separated by whitespace. If an
     argument contains spaces, you must enclose that argument in quotes.</p>
 
     <p>Directives in the configuration files are case-insensitive,
     but arguments to directives are often case sensitive. Lines
     that begin with the hash character "#" are considered
     comments, and are ignored. Comments may <strong>not</strong> be
-    included on the same line as a configuration directive. 
+    included on the same line as a configuration directive.
     White space occurring before a directive is ignored, so
     you may indent directives for clarity. Blank lines are also ignored.</p>
 

Modified: httpd/httpd/trunk/docs/manual/developer/hooks.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/developer/hooks.html.en?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/developer/hooks.html.en (original)
+++ httpd/httpd/trunk/docs/manual/developer/hooks.html.en Wed Apr 15 20:16:24 2015
@@ -29,9 +29,9 @@
       date.</p>
     </div>
 
-    <p>In general, a hook function is one that the Apache HTTP Server 
-    will call at some point during the processing of a request. 
-    Modules can provide functions that are called, and specify when 
+    <p>In general, a hook function is one that the Apache HTTP Server
+    will call at some point during the processing of a request.
+    Modules can provide functions that are called, and specify when
     they get called in comparison to other modules.</p>
 </div>
 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif"
/> <a href="#create">Creating a hook function</a></li>
@@ -103,7 +103,7 @@
 
         <p>The first hook that does <em>not</em> return <code>DECLINED</code>
         stops the loop and its return value is returned from the hook
-        caller. Note that <code>DECLINED</code> is the traditional 
+        caller. Note that <code>DECLINED</code> is the traditional
         hook return value meaning "I didn't do anything", but it can be
         whatever suits you.</p>
 
@@ -181,7 +181,7 @@ mode MODULE_VAR_EXPORT my_module =
       order relative to each other, but, of course, all modules using
       <code>APR_HOOK_FIRST</code> will be run before <code>APR_HOOK_MIDDLE</code>
       which are before <code>APR_HOOK_LAST</code>. Modules that don't care
-      when they are run should use <code>APR_HOOK_MIDDLE</code>. <em>These

+      when they are run should use <code>APR_HOOK_MIDDLE</code>. <em>These
       values are spaced out, so that positions like <code>APR_HOOK_FIRST-2</code>
       are possible to hook slightly earlier than other functions.</em></p>
 

Modified: httpd/httpd/trunk/docs/manual/developer/hooks.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/developer/hooks.xml?rev=1673947&r1=1673946&r2=1673947&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/developer/hooks.xml (original)
+++ httpd/httpd/trunk/docs/manual/developer/hooks.xml Wed Apr 15 20:16:24 2015
@@ -31,9 +31,9 @@
       date.</p>
     </note>
 
-    <p>In general, a hook function is one that the Apache HTTP Server 
-    will call at some point during the processing of a request. 
-    Modules can provide functions that are called, and specify when 
+    <p>In general, a hook function is one that the Apache HTTP Server
+    will call at some point during the processing of a request.
+    Modules can provide functions that are called, and specify when
     they get called in comparison to other modules.</p>
 </summary>
 
@@ -106,7 +106,7 @@ void ap_run_do_something(request_rec *r,
 
         <p>The first hook that does <em>not</em> return <code>DECLINED</code>
         stops the loop and its return value is returned from the hook
-        caller. Note that <code>DECLINED</code> is the traditional 
+        caller. Note that <code>DECLINED</code> is the traditional
         hook return value meaning "I didn't do anything", but it can be
         whatever suits you.</p>
 
@@ -188,7 +188,7 @@ mode MODULE_VAR_EXPORT my_module =
       order relative to each other, but, of course, all modules using
       <code>APR_HOOK_FIRST</code> will be run before <code>APR_HOOK_MIDDLE</code>
       which are before <code>APR_HOOK_LAST</code>. Modules that don't care
-      when they are run should use <code>APR_HOOK_MIDDLE</code>. <em>These

+      when they are run should use <code>APR_HOOK_MIDDLE</code>. <em>These
       values are spaced out, so that positions like <code>APR_HOOK_FIRST-2</code>
       are possible to hook slightly earlier than other functions.</em></p>
 
@@ -220,4 +220,3 @@ static void register_hooks()
     </section>
 </section>
 </manualpage>
-



Mime
View raw message