RFC 7239, "Forwarded HTTP Extension", June 2014

Errata ID: 7973
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Kevin W. Finkenbinder
Date Reported: 2024-06-07
Rejected by: Orie Steele
Date Rejected: 2024-06-19

Section 4 says:

       Forwarded: for="_gazonk"
       Forwarded: For="[2001:db8:cafe::17]:4711"

It should say:

       Forwarded: for="_gazonk"
       Forwarded: for="[2001:db8:cafe::17]:4711"

Notes:

having an example that shows the parameter capitalized indicates that this would be acceptable usage, but nowhere else in the document indicates or implies that this parameter can be capitalized.
--VERIFIER NOTES--
> The top-level list is represented as a list of HTTP header
> field-values as defined in Section 3.2 of [RFC7230]. The first
> element in this list holds information added by the first proxy that
> implements and uses this header field, and each subsequent element
> holds information added by each subsequent proxy. Because this
> header field is optional, any proxy in the chain may choose not to
> update this header field. Each field-value is a semicolon-separated
> list; this sublist consists of parameter-identifier pairs.
> Parameter-identifier pairs are grouped together by an equals sign.
> Each parameter MUST NOT occur more than once per field-value. The
> parameter names are case-insensitive. The header field value can be
> defined in ABNF syntax as:

"The parameter names are case-insensitive".

Report New Errata