RFC Errata
RFC 7234, "Hypertext Transfer Protocol (HTTP/1.1): Caching", June 2014
Note: This RFC has been obsoleted by RFC 9111
Source of RFC: httpbis (wit)
Errata ID: 4616
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Brian Chang
Date Reported: 2016-02-08
Rejected by: Alexey Melnikov
Date Rejected: 2017-02-23
Throughout the document, when it says:
(See Section 3.2 for additional details related to the use of public in response to a request containing Authorization, and Section 3 for details of how public affects responses that would normally not be stored, due to their status codes not being defined as cacheable by default; see Section 4.2.2.) has a status code that is defined as cacheable by default (see Section 4.2.2), or
It should say:
(See Section 3.2 for additional details related to the use of public in response to a request containing Authorization, and Section 3 for details of how public affects responses that would normally not be stored, due to their status codes not being defined as cacheable by default; see Section 6.1 of [RFC7231].) has a status code that is defined as cacheable by default (see Section 6.1 of [RFC7231]), or
Notes:
Section 4.2.2 is titled "Calculating Heuristic Freshness" but is referenced in the original text when talking about status codes. This is confusing despite having a reference to Section 6.1 of RFC7231 buried within the text.
There are other references to 4.2.2 as well, but those actually talk about heuristic freshness.
--VERIFIER NOTES--
See HTTPBIS mailing list discussion.