RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

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

Source of RFC: httpbis (app)

Errata ID: 5162
Status: Verified
Type: Editorial

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: Reported (1)

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

Source of RFC: httpbis (app)

Errata ID: 5236
Status: Reported
Type: Technical

Reported By: Chris Pacejo
Date Reported: 2018-01-16

Section 2.1 says:

Likewise, a validator is weak if it is shared by two or more
representations of a given resource at the same time, unless those
representations have identical representation data.  For example, if
the origin server sends the same validator for a representation with
a gzip content coding applied as it does for a representation with no
content coding, then that validator is weak.  However, two
simultaneous representations might share the same strong validator if
they differ only in the representation metadata, such as when two
different media types are available for the same representation data.

It should say:

Likewise, a validator is weak if it is shared by two or more
representations of a given resource at the same time, even if those
representations have identical representation data.  For example, if
the origin server sends the same validator for a representation with
a gzip content coding applied as it does for a representation with no
content 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."

Report New Errata