- From: vanupam <notifications@github.com>
- Date: Mon, 06 Feb 2017 19:12:16 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 7 February 2017 03:12:50 UTC
vanupam commented on this pull request. > @@ -1363,6 +1419,16 @@ <h4 id=terminology-headers>Headers</h4> <p>Let <var>connection</var> be the result of establishing an HTTP connection to <var>origin</var>. <span data-anolis-ref>HTTP</span> <span data-anolis-ref>TLS</span> + <p>If <var>credentials</var> is true and if the user agent supports + <span title=concept-token-binding>Token Binding</span>, propose the use of Token Binding for the + TLS connection by adding a Token Binding Negotiation extension in the TLS Client Hello as + described in + <a href="https://tools.ietf.org/html/draft-ietf-tokbind-negotiation#section-2">section 2</a> + of the Token Binding Negotiation spec. + + <p class="note no-backref">If Token Binding Negotiation succeeds, the user agent can use + <span title=concept-token-binding>Token Binding</span> with the server. I will revisit this, if it is still needed after the refactor. -- 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/pull/325
Received on Tuesday, 7 February 2017 03:12:50 UTC