Search RFCs

RFC Editor

Found 2 records.

Status:Verified (1)

RFC 7232, "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests", June 2014

Note: This RFC has been obsoleted byRFC 9110

Errata ID:5162
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Julian Reschke
Date Reported: 2017-10-20
Verifier Name: Alexey Melnikov
Date Verified: 2017-10-20

Section A says:

   The ETag header field ABNF has been changed to not use quoted-string,   thus avoiding escaping issues.  (Section 2.3)

It should say:

   The ETag header field ABNF has been changed to not use quoted-string,   thus avoiding escaping issues. Furthermore, it now disallows the   space character. (Section 2.3)

Notes:

(This entry in the changes section is incomplete)

Status:Rejected (1)

RFC 7232, "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests", June 2014

Note: This RFC has been obsoleted byRFC 9110

Errata ID:5236
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Chris Pacejo
Date Reported: 2018-01-16
Rejected by: Barry Leiba
Date Rejected: 2020-08-27

Section 2.1 says:

Likewise, a validator is weak if it is shared by two or morerepresentations of a given resource at the same time, unless thoserepresentations have identical representation data.  For example, ifthe origin server sends the same validator for a representation witha gzip content coding applied as it does for a representation with nocontent coding, then that validator is weak.  However, twosimultaneous representations might share the same strong validator ifthey differ only in the representation metadata, such as when twodifferent media types are available for the same representation data.

It should say:

Likewise, a validator is weak if it is shared by two or morerepresentations of a given resource at the same time, even if thoserepresentations have identical representation data.  For example, ifthe origin server sends the same validator for a representation witha gzip content coding applied as it does for a representation with nocontent coding, then that validator is weak.

Notes:

This paragraph (and only this paragraph) seems to be in direct conflict with this earlier text from the same section:

"However, if a resource has distinct representations that differ only in their metadata, such as might occur with content negotiation over media types that happen to share the same data format, then the origin server needs to incorporate additional information in the [strong] validator to distinguish those representations."
--VERIFIER NOTES--
There is not a conflict here: The text quoted in the notes needs to be read in the context of the entire paragraph it appears in, which the "however" references. The quoted statement is being made in the context of generating strong validators based only upon the message body, when the headers might also change.

Report New Errata