You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2013/08/23 16:37:10 UTC
svn commit: r1516864 - /httpd/httpd/trunk/docs/manual/mod/mod_cache.xml
Author: covener
Date: Fri Aug 23 14:37:09 2013
New Revision: 1516864
URL: http://svn.apache.org/r1516864
Log:
s/authorisation/authorization/ for consistency with the rest of this
doc and manual
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_cache.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_cache.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_cache.xml?rev=1516864&r1=1516863&r2=1516864&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_cache.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_cache.xml Fri Aug 23 14:37:09 2013
@@ -246,14 +246,14 @@ LoadModule cache_module modules/mod_cach
<p>While this mode offers the best performance, the administrator may find that
under certain circumstances they may want to perform further processing on the
request after the request is cached, such as to inject personalisation into the
- cached page, or to apply authorisation restrictions to the content. Under these
+ cached page, or to apply authorization restrictions to the content. Under these
circumstances, an administrator is often forced to place independent reverse
proxy servers either behind or in front of the caching server to achieve this.</p>
<p>To solve this problem the <directive module="mod_cache">CacheQuickHandler
</directive> directive can be set to <strong>off</strong>, and the server will
process all phases normally handled by a non-cached request, including the
- <strong>authentication and authorisation</strong> phases.</p>
+ <strong>authentication and authorization</strong> phases.</p>
<p>In addition, the administrator may optionally specify the <strong>precise point
within the filter chain</strong> where caching is to take place by adding the
@@ -926,7 +926,7 @@ CacheLock on
<p>When disabled, the cache operates as a normal handler, and is subject to
the full set of phases when handling a server request. While this mode is
slower than the default, it allows the cache to be used in cases where full
- processing is required, such as when content is subject to authorisation.</p>
+ processing is required, such as when content is subject to authorization.</p>
<highlight language="config">
# Run cache as a normal handler