From dd7a9513d21b5e4c8a4571c909828bf002afaabe Mon Sep 17 00:00:00 2001 From: Patrick McManus Date: Mon, 13 Mar 2017 12:04:11 -0400 Subject: [PATCH] issue 289 - place normative requirement on client side --- draft-ietf-httpbis-immutable.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/draft-ietf-httpbis-immutable.md b/draft-ietf-httpbis-immutable.md index c56e8263b..c9ae403ed 100644 --- a/draft-ietf-httpbis-immutable.md +++ b/draft-ietf-httpbis-immutable.md @@ -89,8 +89,13 @@ skipped without worrying that it has been updated. # The immutable Cache-Control extension When present in an HTTP response, the immutable Cache-Control -extension indicates that the origin server MUST NOT update the representation -of that resource during the freshness lifetime of the response. +extension indicates that the origin server will not update the representation +of that resource during the freshness lifetime of the +response. + +Clients SHOULD NOT issue a conditional request during the +response's freshness lifetime (e.g. upon a reload) unless explicitly +overridden by the user (e.g. a force reload). The immutable extension only applies during the freshness lifetime of the response. Stale responses SHOULD be revalidated as they normally