Author: Henrik Nordstrom <henrik@henriknordstrom.net>

Bug #1955: Clarify refresh_pattern override-expire option

override-expire applies to both Expires and CC max-age, but comments
only mention Expires..

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 2fd3f3675de534286a621d5eba3541dd50ef3ba2..c44a29afb1b62fda84ea68df6f4472dec9638048 100644 (file)
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -2520,9 +2520,10 @@ DOC_START
                 refresh-ims
 
                override-expire enforces min age even if the server
-               sent a Expires: header. Doing this VIOLATES the HTTP
-               standard.  Enabling this feature could make you liable
-               for problems which it causes.
+               sent an explicit expiry time (e.g., with the
+               Expires: header or Cache-Control: max-age). Doing this
+               VIOLATES the HTTP standard.  Enabling this feature
+               could make you liable for problems which it causes.
 
                override-lastmod enforces min age even on objects
                that were modified recently.