Opened 5 years ago

Closed 5 years ago

#431 closed design (fixed)

origin-form does not allow path starting with "//"

Reported by: julian.reschke@… Owned by:
Priority: normal Milestone: 22
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:

Description (last modified by julian.reschke@…)

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 ""

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.

Attachments (1)

431.diff (6.5 KB) - added by julian.reschke@… 5 years ago.
Proposed patch

Download all attachments as: .zip

Change History (6)

comment:1 Changed 5 years ago by julian.reschke@…

  • Description modified (diff)

Changed 5 years ago by julian.reschke@…

Proposed patch

comment:2 Changed 5 years ago by julian.reschke@…

From [2181]:

allow origin-form to use a path starting with "" (see #431)

comment:3 Changed 5 years ago by julian.reschke@…

  • Milestone changed from unassigned to 22
  • Resolution set to incorporated
  • Status changed from new to closed

comment:4 Changed 5 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 5 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.