httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rbo...@apache.org
Subject svn commit: r413494 - in /httpd/httpd/trunk/docs/manual: caching.html.en caching.xml
Date Sun, 11 Jun 2006 18:20:04 GMT
Author: rbowen
Date: Sun Jun 11 11:20:04 2006
New Revision: 413494

URL: http://svn.apache.org/viewvc?rev=413494&view=rev
Log:
Typo correction.
Submitted by Vincent 'noodl' Bray.

Modified:
    httpd/httpd/trunk/docs/manual/caching.html.en
    httpd/httpd/trunk/docs/manual/caching.xml

Modified: httpd/httpd/trunk/docs/manual/caching.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/caching.html.en?rev=413494&r1=413493&r2=413494&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/caching.html.en (original)
+++ httpd/httpd/trunk/docs/manual/caching.html.en Sun Jun 11 11:20:04 2006
@@ -297,7 +297,7 @@
 <h2><a name="security" id="security">Security Considerations</a></h2>
     
 
-    <h3>Authorisation, Access &amp; and Control</h3>
+    <h3>Authentication, Authorization and Access Control</h3>
       
 
       <p>Using <code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>
is very much like having a built
@@ -314,8 +314,8 @@
       from the cache as long as that content has not expired.</p>
 
       <p>If, for example, your configuration permits access to a resource by IP
-      address you should ensure that this content is not cached. You can do this by
-      using the <code class="directive"><a href="./mod/mod_cache.html#cachedisable">CacheDisable</a></code>
+      address you should ensure that this content is not cached. You can do this
+      by using the <code class="directive"><a href="./mod/mod_cache.html#cachedisable">CacheDisable</a></code>
       directive, or <code class="module"><a href="./mod/mod_expires.html">mod_expires</a></code>.
Left unchecked,
       <code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code>
- very much like a reverse proxy - would cache
       the content when served and then serve it to any client, on any IP

Modified: httpd/httpd/trunk/docs/manual/caching.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/caching.xml?rev=413494&r1=413493&r2=413494&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/caching.xml (original)
+++ httpd/httpd/trunk/docs/manual/caching.xml Sun Jun 11 11:20:04 2006
@@ -319,7 +319,7 @@
     <title>Security Considerations</title>
 
     <section>
-      <title>Authorisation, Access &amp; and Control</title>
+      <title>Authentication, Authorization and Access Control</title>
 
       <p>Using <module>mod_cache</module> is very much like having a built
       in reverse-proxy. Requests will be served by the caching module unless
@@ -335,8 +335,8 @@
       from the cache as long as that content has not expired.</p>
 
       <p>If, for example, your configuration permits access to a resource by IP
-      address you should ensure that this content is not cached. You can do this by
-      using the <directive module="mod_cache">CacheDisable</directive>
+      address you should ensure that this content is not cached. You can do this
+      by using the <directive module="mod_cache">CacheDisable</directive>
       directive, or <module>mod_expires</module>. Left unchecked,
       <module>mod_cache</module> - very much like a reverse proxy - would cache
       the content when served and then serve it to any client, on any IP



Mime
View raw message