You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2026/04/03 12:18:46 UTC

svn commit: r1932787 - httpd/httpd/branches/2.4.x/docs/manual/mod

Author: rbowen
Date: Fri Apr  3 12:18:46 2026
New Revision: 1932787

Log:
Resolves bz59658 - Bring CacheIgnoreNoLastMod doc in line with actual
behavior.

Modified:
   httpd/httpd/branches/2.4.x/docs/manual/mod/mod_cache.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_cache.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_cache.xml	Fri Apr  3 12:16:47 2026	(r1932786)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_cache.xml	Fri Apr  3 12:18:46 2026	(r1932787)
@@ -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>