- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 22 Oct 2014 18:31:28 +0200
- To: Ilya Grigorik <igrigorik@google.com>
- Cc: Mark Nottingham <mnot@mnot.net>, William Chan (ιζΊζ) <willchan@chromium.org>, Peter Lepeska <bizzbyster@gmail.com>, Tobin Titus <tobint@microsoft.com>, Patrick McManus <pmcmanus@mozilla.com>, public-web-perf <public-web-perf@w3.org>, Tony Gentilcore <tonyg@chromium.org>
On Wed, Oct 22, 2014 at 6:25 PM, Ilya Grigorik <igrigorik@google.com> wrote:
> Anne: thinking about this some more, it seems like "protocol" in Fetch has
> it backwards. Historically, yes, you could just look at the scheme and infer
> the protocol (http or https), but that is no longer the case because https
> --> {http/1.1, http/2, spdy/.., quic/..., ...}. If anything, I'd argue we
> should drop "protocol" (we still have "scheme") from URL because you don't
> actually know the protocol until the connection is negotiated. In other
> words, moving forward URL.protocol will be lying most of the time.
Fetch doesn't use "protocol". The API we have had for URL manipulation
(defined in URL) for two decades or so has it and that is unlikely to
change.
--
https://annevankesteren.nl/
Received on Wednesday, 22 October 2014 16:31:59 UTC