Thanks for the quick response :-) I'm a bit confused now: Is the form "transfer-parameter = token" allowed as the test suggests, or is it disallowed as the ABNF suggests? Thanks Etan > On 23 Oct 2016, at 10:12, Julian Reschke <julian.reschke@greenbytes.de <mailto:julian.reschke@greenbytes.de>> wrote: > > On 2016-10-23 01:10, RFC Errata System wrote: >> The following errata report has been submitted for RFC7230, >> "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". >> >> -------------------------------------- >> You may review the report below and at: >> http://www.rfc-editor.org/errata_search.php?rfc=7230&eid=4838 <http://www.rfc-editor.org/errata_search.php?rfc=7230&eid=4838> >> >> -------------------------------------- >> Type: Technical >> Reported by: Etan Kissling <etan.kissling@gmail.com> >> >> Section: 4 >> >> Original Text >> ------------- >> Parameters are in the form of a name or name=value pair. >> >> transfer-parameter = token BWS "=" BWS ( token / quoted-string ) >> >> Corrected Text >> -------------- >> Parameters are in the form of a name or name=value pair. >> >> transfer-parameter = token >> / token BWS "=" BWS ( token / quoted-string ) >> >> Notes >> ----- >> The form of a name cannot be represented with the original ABNF. >> ... > > > That's true, but that doesn't mean it's an erratum. If's defined this way intentionally, and also hasn't changed compared to RFC 2616. > > Best regards, Julian
Received on Monday, 24 October 2016 08:37:48 UTC