Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)

> +              origin executes in the user agent.  The user agent would have negotiated the use of
> +              Token Binding with that server when it set up the 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>.
> +            <li><p>If <var>referredTokenBindingId</var> is different from
> +              <var>providedTokenBindingId</var>, then add <var>referredTokenBindingId</var> as a
> +              <code title="">referred_token_binding</code> to <var>tokenBindingMessage</var>.
> +          </ol>
> +
> +          <li><p>If <var>tokenBindingMessage</var> is not <var>null</var>, append a

Null is not a variable.

-- 
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/files/134b9885c84ccdb9656767e4b369adf010363795#r76749287