- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 24 Jul 2014 13:30:52 -0400
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Matthew Kerwin <matthew@kerwin.net.au>, Adrien de Croy <adrien@qbik.com>, Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
As per our other decisions recently, this is too speculative to include in HTTP/2 at this late stage. Happy for the discussion to continue for the benefit of future work, but the underlying issue for HTTP/2 has been closed. Cheers, On 24 Jul 2014, at 2:18 am, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: > In message <CACweHNC9rP3i=-VxRJQkHPLjkXnjbbqMAoF8TpSWnMobrC-TdQ@mail.gmail.com> > , Matthew Kerwin writes: > >> I could see some interest in splitting the path into either a single "*" or >> a list of segments (removing "%2F" from the path string), but for one how >> many URLs have %2F in the path? And for two the rules in RFC 3986 and a >> couple of decades of experience already have that covered, I think. >> >> I guess you could split the authority into userinfo/host/port if you were >> desperate for such a thing. > > Uhmm, lets not go overboard here, please ? > > I'm proposing splitting :query for :path, because it is a well known > distinction which through its established use-pattern gives us a > handy way to improve compression significantly in common scenarios. > > We already split the HTTP URL into it's other major parts, :scheme, > :authority and :path, so splitting out the last major part is not > a big step and involves neither complex text nor introduces a lot > of error handling. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Mark Nottingham http://www.mnot.net/
Received on Thursday, 24 July 2014 17:31:22 UTC