- From: vanupam <notifications@github.com>
- Date: Mon, 06 Feb 2017 19:14:37 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/325/review/20422518@github.com>
vanupam commented on this pull request. > + <span title=concept-token-binding-id>Token Binding Id</span> + for the <var>httpRequest</var>'s + <span title=concept-request-referred-token-binding-origin>referred-token-binding-origin</span>. + <p class="note no-backref">A server indicates that it wants the user agent to use a + Referred Token Binding when doing a redirect to another server, + or when code from that server's origin executes in the user agent. + The user agent would have negotiated the use of + Token Binding with that server when it set up a TLS connection to that server, + creating a <span title=concept-token-binding-id>Token Binding Id</span> + at the end of the negotiation. + This <span title=concept-token-binding-id>Token Binding Id</span> is saved and can + then simply be looked up whenever needed. If the + <span title=concept-token-binding-id>Token Binding Id</span> for the server is + deleted by a user agent (e.g., as a result of some user action), the user agent will + need to re-establish a TLS connection to negotiate Token Binding and create a new + <span title=concept-token-binding-id>Token Binding Id</span>. Done. -- 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:15:09 UTC