Resolves bz59658 - Bring CacheIgnoreNoLastMod doc in line with actual

behavior.

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

diff --git a/docs/manual/mod/mod_cache.xml b/docs/manual/mod/mod_cache.xml
index 23471d828a15bf67625805db8998f393817ab06f..329fad81a76ca20d261623c53b2cf9c68716b258 100644 (file)
--- a/docs/manual/mod/mod_cache.xml
+++ b/docs/manual/mod/mod_cache.xml
@@ -550,6 +550,13 @@ header.</description>
     <directive module="mod_cache">CacheDefaultExpire</directive> directive will be used to
     generate an expiration date.</p>
 
+    <note>More precisely, a 200 OK response is only cached if it includes
+    at least one of the <code>Last-Modified</code>, <code>ETag</code>,
+    or <code>Expires</code> headers, or a <code>Cache-Control: max-age</code>
+    or <code>s-maxage</code> directive. This directive bypasses that
+    requirement entirely. When any of those headers are already present,
+    this directive has no effect.</note>
+
     <highlight language="config">
       CacheIgnoreNoLastMod On
     </highlight>