Ticket #431 (closed design: fixed)
origin-form does not allow path starting with "//"
|Reported by:||firstname.lastname@example.org||Owned by:|
|Component:||p1-messaging||Severity:||In WG Last Call|
Description (last modified by email@example.com) (diff)
Zong Yu reports:
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 ""
origin-form = path-absolute [ "?" query ]
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.
- Status changed from new to closed
- Resolution set to incorporated
- Milestone changed from unassigned to 22
- Status changed from closed to reopened
- Resolution incorporated deleted