- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 08 Feb 2013 18:05:37 +0100
- To: Zhong Yu <zhong.j.yu@gmail.com>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2013-02-01 19:37, Zhong Yu wrote: > If user clicks a URL http://example.com//abc, the browser should send > > GET //abc HTTP/1.1 > Host: example.com > > However the latest bis draft seems to forbid "origin-form" to start with "//" > > http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-5.3 > > origin-form = path-absolute [ "?" query ] > > http://tools.ietf.org/html/rfc3986#section-3.3 > > path-absolute ; begins with "/" but not "//" > > I couldn't find anything in RFC 3986 that accurately describe the path > part that we really want, which should be > > path-xxx = "/" *( "/" / pchar ) > > HTTP probably need to define this term. It'll also help people to > finally refer to this thingy with a proper name. > > Zhong Yu We have origin-form = path-absolute [ "?" query ] with path-absolute = "/" [ segment-nz *( "/" segment ) ] ; <http://greenbytes.de/tech/webdav/rfc3986.html#path> Using origin-form = "/" [ segment *( "/" segment ) ] [ "?" query ] ...seems to be the minimal change (or can we simplify that production further without losing readability?) Best regards, Julian
Received on Friday, 8 February 2013 17:06:08 UTC