RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (2)

RFC 7240, "Prefer Header for HTTP", June 2014

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 4439

Status: Verified
Type: Technical

Reported By: Martin Thomson
Date Reported: 2015-08-09
Verifier Name: Barry Leiba
Date Verified: 2016-02-23

Section 2 says:

     preference = token [ BWS "=" BWS word ]
                  *( OWS ";" [ OWS parameter ] )
     parameter  = token [ BWS "=" BWS word ]

It should say:

     preference = preference-parameter *( OWS ";" [ OWS
                  preference-parameter ] )
     preference-parameter = parameter / token

Notes:

Section 1.1 incorrectly states that "word" is defined in RFC 7230. It is not. Therefore, the syntax is completely under-specified.

The "parameter" rule, as defined in RFC 7231, is used in lots of other header field definitions successfully. The only drawback is that "parameter" doesn't permit the use of "OWS" either side of the "=" character.

This change would also require changes to Section 1.1.

Errata ID: 4316

Status: Verified
Type: Editorial

Reported By: Matthew Kerwin
Date Reported: 2015-03-27
Verifier Name: Barry Leiba
Date Verified: 2015-03-28

Section 1.1 says:

within Sections 3.2.1 and 3.2.4 of [RFC7230]; as well as the
"delta-seconds" rule defined in Section 8.1.3 of [RFC7231].

It should say:

within Sections 3.2.1 and 3.2.4 of [RFC7230]; as well as the
"delay-seconds" rule defined in Section 7.1.3 of [RFC7231].

Notes:

The reference to "delta-seconds" seems to come from an earlier version of the HTTP-bis draft. This was changed to "delay-seconds" in later versions, and the section number changed.

Status: Reported (2)

RFC 7240, "Prefer Header for HTTP", June 2014

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 4625

Status: Reported
Type: Technical

Reported By: Vasiliy Faronov
Date Reported: 2016-02-24

Section 3 says:

     applied-pref = token [ BWS "=" BWS word ]

It should say:

     applied-pref = preference-parameter
                    ; see Errata ID: 4439

Notes:

This updates the syntax of the Preference-Applied header field in accordance with a previous erratum to this document, which fixed the Prefer header field.

Errata ID: 4955

Status: Reported
Type: Technical

Reported By: Vasiliy Faronov
Date Reported: 2017-03-01

Section 2.1 says:

     Prefer: Lenient

It should say:

     Prefer: Handling="lenient"

Notes:

"Prefer: Lenient" is a valid header that specifies an (unregistered) preference named "lenient" with an empty value.

On the other hand, this document defines a preference named "handling", which can take the value "lenient" to indicate lenient processing, which is the stated intent of this example.

There is no provision for specifying a preference by its *value*, as opposed to by its *name*.

Status: Rejected (1)

RFC 7240, "Prefer Header for HTTP", June 2014

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 4317

Status: Rejected
Type: Editorial

Reported By: Brendan Long
Date Reported: 2015-03-30
Rejected by: Barry Leiba
Date Rejected: 2015-04-02

Throughout the document, when it says:

Prefer: respond-async, wait=100
Prefer: handling=lenient

Prefer: handling=lenient, wait=100, respond-async

Prefer: respond-async, wait=10
Prefer: priority=5

Prefer: respond-async, wait=10

It should say:

Prefer: respond-async; wait=100
Prefer: handling=lenient

Prefer: handling=lenient; wait=100; respond-async

Prefer: respond-async; wait=10
Prefer: priority=5

Prefer: respond-async; wait=10

Notes:

The ABNF in Section 2 says that preferences are separated with ";", but some of the examples use ",".
--VERIFIER NOTES--
The document is correct as is stands. The commas are separating
multiple preferences in a single header, as described in RFC 7230,
Section 7. The ABNF in Section 2 specifies how to separate parameters
within a single preference.

Report New Errata