Re: [whatwg/fetch] section #connections is vague wrt connection is HTTP or HTTPS or HTTP/2 or QUIC (#641) from sleevi on 2017-11-30 (public-webapps-github@w3.org from November 2017)

From: sleevi <notifications@github.com>
Date: Thu, 30 Nov 2017 14:55:53 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/641/348347808@github.com>

@equalsJeffH I'm working on Chrome's implementation of this, but I'm unclear about what the implications of this are?

That is, at least as implemented in Chrome (and others, from what I've seen), whether or not to send a certificate is somewhat of a state independent of the underlying transport, and the underlying transport doesn't support certificates, it simply doesn't send them.

Is the concern about it being specific to TLS? Would it also work to say: "If credentials is false, do not send a certificate" (e.g. omitting TLS to support QUIC or HTTP/2 certificate frames, and omitting client to avoid any ambiguity about what type of certificate)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/641#issuecomment-348347808

Received on Thursday, 30 November 2017 22:56:15 UTC