W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2019

[Editorial Errata Reported] RFC7230 (5623)

From: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Tue, 5 Feb 2019 08:11:27 -0800 (PST)
To: fielding@gbiv.com, julian.reschke@greenbytes.de, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, mnot@mnot.net, patrick.ducksong@gmail.com, tpauly@apple.com
Cc: a.abfalterer@gmail.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Message-Id: <20190205161127.7B9BAB80A02@rfc-editor.org>
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:

Type: Editorial
Reported by: Armin Abfalterer <a.abfalterer@gmail.com>

Section: 2.7

Original Text
absolute-URI  = <absolute-URI, see [RFC3986], Section 4.3>

Corrected Text

RFC3986 defines "absolute-URI" very openly, especially regarding to "hier-part":

      absolute-URI  = scheme ":" hier-part [ "?" query ]

      hier-part   = "//" authority path-abempty
                  / path-absolute
                  / path-rootless
                  / path-empty

The impact is reflected in RFC 7231 in the definition of the header fields Referer and Content-Location.

      absolute-URI = <absolute-URI, see [RFC7230], Section 2.7>

Thus, following examples of header values are considered valid

Referer: https:foo/bar
Referer: https:/foo
Referer: https:/
Referer: foo:/

I'd suggest to define "hier-part" (but also "scheme") more strictly.

This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

RFC7230 (draft-ietf-httpbis-p1-messaging-26)
Title               : Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Publication Date    : June 2014
Author(s)           : R. Fielding, Ed., J. Reschke, Ed.
Category            : PROPOSED STANDARD
Source              : Hypertext Transfer Protocol Bis APP
Area                : Applications
Stream              : IETF
Verifying Party     : IESG
Received on Tuesday, 5 February 2019 16:12:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 February 2019 16:12:27 UTC