RFC Errata
Found 3 records.
Status: Reported (2)
RFC 7239, "Forwarded HTTP Extension", June 2014
Source of RFC: appsawg (app)
Errata ID: 5067
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Vasiliy Faronov
Date Reported: 2017-07-12
Throughout the document, when it says:
proxy
It should say:
message-forwarding agent
Notes:
According to RFC 7230 Section 2.3, an HTTP "proxy" is a message-forwarding agent that is selected by the client. But this specification (as is clear from Section 1) uses the word "proxy" to refer also to message-forwarding agents that are *not* selected by the client.
Errata ID: 5275
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: W. Trevor King
Date Reported: 2018-03-06
Section 4 says:
Forwarded = 1#forwarded-element
It should say:
Forwarded = forwarded-element *(OWS "," OWS forwarded-element) OWS = <Defined in [RFC7230], Section 3.2.3>
Notes:
Currently the only mention of commas in the RFC is in the text:
> A proxy server that wants to add a new "Forwarded" header field value can either append it to the last existing "Forwarded" header field after a comma separator or add a new field at the end of the header block.
This should be reflected in the ABNF. The original ABNF suggests you just smash the forwarded-elements together with no delimiters.
Status: Rejected (1)
RFC 7239, "Forwarded HTTP Extension", June 2014
Source of RFC: appsawg (app)
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".