You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by no...@apache.org on 2009/04/18 16:05:40 UTC
svn commit: r766324 - /httpd/httpd/trunk/docs/manual/caching.xml
Author: noodl
Date: Sat Apr 18 14:05:40 2009
New Revision: 766324
URL: http://svn.apache.org/viewvc?rev=766324&view=rev
Log:
Grammar and whitespace cleanup
Modified:
httpd/httpd/trunk/docs/manual/caching.xml
Modified: httpd/httpd/trunk/docs/manual/caching.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/caching.xml?rev=766324&r1=766323&r2=766324&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/caching.xml (original)
+++ httpd/httpd/trunk/docs/manual/caching.xml Sat Apr 18 14:05:40 2009
@@ -286,7 +286,7 @@
not be cached.</p>
<p>If on the other hand, the content served differs depending on the
- values of various HTTP headers, it is possible that it might be possible
+ values of various HTTP headers, it might be possible
to cache it intelligently through the use of a "Vary" header.</p>
</section>
@@ -307,10 +307,9 @@
</example>
<p><module>mod_cache</module> will only serve the cached content to
- requesters with matching accept-language and accept-charset headers
+ requesters with accept-language and accept-charset headers
matching those of the original request.</p>
</section>
-
</section>
<section id="security">
@@ -338,7 +337,7 @@
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
- address.</p>
+ address.</p>
</section>
<section>