From 034c337f4e13c83aa6322f14cb7b58ffb2b435ae Mon Sep 17 00:00:00 2001 From: "Roy T. Fielding" Date: Fri, 22 Nov 2019 15:28:15 +0800 Subject: [PATCH] fix #264 must-revalidate paste-o --- draft-ietf-httpbis-cache-latest.html | 30 ++++++++++++++-------------- draft-ietf-httpbis-cache-latest.xml | 2 +- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/draft-ietf-httpbis-cache-latest.html b/draft-ietf-httpbis-cache-latest.html index 5a3bf3325..8edbf781c 100644 --- a/draft-ietf-httpbis-cache-latest.html +++ b/draft-ietf-httpbis-cache-latest.html @@ -612,7 +612,7 @@ content: "Fielding, et al."; } @bottom-center { - content: "Expires May 23, 2020"; + content: "Expires May 25, 2020"; } @bottom-right { content: "[Page " counter(page) "]"; @@ -653,7 +653,7 @@ - + @@ -680,7 +680,7 @@ Fastly - Expires: May 23, 2020 + Expires: May 25, 2020 J. Reschke, Editor @@ -689,7 +689,7 @@ - November 20, 2019 + November 22, 2019 @@ -743,7 +743,7 @@

Status of This Memo

Internet-Drafts as reference material or to cite them other than as “work in progress”.

-

This Internet-Draft will expire on May 23, 2020.

+

This Internet-Draft will expire on May 25, 2020.

@@ -1156,7 +1156,7 @@

4. Section 5.3 of [Semantics]) and that of the stored response match, and +

The presented effective request URI (Section 5.4 of [Semantics]) and that of the stored response match, and

@@ -1667,15 +1667,15 @@

4.4. 

-

A cache MUST invalidate the effective Request URI (Section 5.3 of [Semantics]) as well as the URI(s) in the Location and Content-Location response header fields (if present) when a non-error status code is received in response +

A cache MUST invalidate the effective Request URI (Section 5.4 of [Semantics]) as well as the URI(s) in the Location and Content-Location response header fields (if present) when a non-error status code is received in response to an unsafe request method.

However, a cache MUST NOT invalidate a URI from a Location or Content-Location response header field if the host part of that URI differs from the host part in the - effective request URI (Section 5.3 of [Semantics]). This helps prevent denial-of-service attacks.

+ effective request URI (Section 5.4 of [Semantics]). This helps prevent denial-of-service attacks.

-

A cache MUST invalidate the effective request URI (Section 5.3 of [Semantics]) when it receives a non-error response to a request with a method whose safety is +

A cache MUST invalidate the effective request URI (Section 5.4 of [Semantics]) when it receives a non-error response to a request with a method whose safety is unknown.

@@ -2068,7 +2068,7 @@
5.2.2.3. 5.2.2.4. no-transform

The "no-transform" response directive indicates that an intermediary (regardless of - whether it implements a cache) MUST NOT transform the payload, as defined in Section 5.5.2 of [Semantics].

+ whether it implements a cache) MUST NOT transform the payload, as defined in Section 5.6.2 of [Semantics].

@@ -2159,8 +2159,8 @@
5.2.2.9. 

-

The must-revalidate directive also has the effect of allowing a stored response to - be used to satisfy a request with an Authorization header field; see Section 3.2.

+

The s-maxage directive also has the effect of allowing a stored response to be used + to satisfy a request with an Authorization header field; see Section 3.2.

This directive uses the token form of the argument syntax: e.g., 's-maxage=10' not @@ -2762,8 +2762,8 @@

Index

  • Section 4.2  4.1
  • Section 4.2.3.1  1.2
  • Section 4.2.3.2  1.2
    • -
  • Section 5.3  4, 4.4, 4.4, 4.4
    • -
  • Section 5.5.2  5.2.1.6, 5.2.2.4
    • +
  • Section 5.4  4, 4.4, 4.4, 4.4
    • +
  • Section 5.6.2  5.2.1.6, 5.2.2.4
  • Section 7.2.1  4, 4.4
  • Section 7.3.1  2
  • Section 8.2  4.3
    • diff --git a/draft-ietf-httpbis-cache-latest.xml b/draft-ietf-httpbis-cache-latest.xml index 78f690602..d2f8295fb 100644 --- a/draft-ietf-httpbis-cache-latest.xml +++ b/draft-ietf-httpbis-cache-latest.xml @@ -1683,7 +1683,7 @@ proxy-revalidate response directive. - The must-revalidate directive also has the effect of allowing a stored + The s-maxage directive also has the effect of allowing a stored response to be used to satisfy a request with an Authorization header field; see .