W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

Fwd: [Technical Errata Reported] RFC2616 (3056)

From: Peter Saint-Andre <stpeter@stpeter.im>
Date: Tue, 20 Dec 2011 16:54:59 -0700
Message-ID: <4EF12053.40205@stpeter.im>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
FYI.

-------- Original Message --------
Subject: [Technical Errata Reported] RFC2616 (3056)
Date: Tue, 20 Dec 2011 15:52:18 -0800 (PST)
From: RFC Errata System <rfc-editor@rfc-editor.org>
To: fielding@ics.uci.edu, jg@w3.org, mogul@wrl.dec.com, frystyk@w3.org,
masinter@parc.xerox.com, paulle@microsoft.com, timbl@w3.org,
presnick@qualcomm.com, stpeter@stpeter.im
CC: julm+rfc@autogeree.net, rfc-editor@rfc-editor.org


The following errata report has been submitted for RFC2616,
"Hypertext Transfer Protocol -- HTTP/1.1".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=2616&eid=3056

--------------------------------------
Type: Technical
Reported by: Julien Moutinho <julm+rfc@autogeree.net>

Section: 5.1.2

Original Text
-------------
Request-URI    = "*" | absoluteURI | abs_path | authority

Corrected Text
--------------
Request-URI    = "*" | absoluteURI | abs_path [ "?" query ] | authority


Notes
-----
so that "/path?query" is a valid Request-URI as it should.

because it is not the case with RFC 3986
(obsoleting RFC 2396 which has the same problem actually):

absoluteURI   = absolute-URI
abs_path      = path-absolute

absolute-URI  = scheme ":" hier-part [ "?" query ]
path-absolute = "/" [ segment-nz *( "/" segment ) ]
segment-nz    = 1*pchar
segment       = *pchar
pchar         = unreserved / pct-encoded / sub-delims / ":" / "@"
unreserved    = ALPHA / DIGIT / "-" / "." / "_" / "~"
pct-encoded   = "%" HEXDIG HEXDIG
sub-delims    = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," /
";" / "="

Instructions:
-------------
This errata 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 (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC2616 (draft-ietf-http-v11-spec-rev-06)
--------------------------------------
Title               : Hypertext Transfer Protocol -- HTTP/1.1
Publication Date    : June 1999
Author(s)           : R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L.
Masinter, P. Leach, T. Berners-Lee
Category            : DRAFT STANDARD
Source              : HyperText Transfer Protocol
Area                : Applications
Stream              : IETF
Verifying Party     : IESG
Received on Tuesday, 20 December 2011 23:55:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:51 GMT