Commit a67b48ca authored by Richard Bowen's avatar Richard Bowen
Browse files

Typo correction. 

Submitted by Vincent 'noodl' Bray.


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

docs/manual/caching.html.en

+3 −3
Original line number Diff line number Diff line
@@ -297,7 +297,7 @@ Vary: negotiate,accept-language,accept-charset 
<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 @@ Vary: negotiate,accept-language,accept-charset 
      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

docs/manual/caching.xml

+3 −3
Original line number Diff line number Diff line
@@ -319,7 +319,7 @@ Vary: negotiate,accept-language,accept-charset 
    <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 @@ Vary: negotiate,accept-language,accept-charset 
      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