| commit | d7c237b9c3efb014b44d07fe7b0e8623335e009e | [log] [tgz] |
|---|---|---|
| author | nharper <nharper@chromium.org> | Wed Mar 30 23:05:48 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Wed Mar 30 23:07:26 2016 |
| tree | eece811b661fd06235dc962a46ac038bd43ea7f0 | |
| parent | 26adb92c655dbf8480c3e03f1e0bdef11de1daad [diff] |
Implement referred Token Bindings As described in https://tools.ietf.org/html/draft-ietf-tokbind-https-02: when a server sends the 'Include-Referer-Token-Binding-ID' header on a redirect response, the client will include the TokenBindingID from the referrer in its request to the new location in the redirect. If either connection does not have Token Binding enabled, then this has no effect. BUG=467312 Review URL: https://codereview.chromium.org/1781003003 Cr-Original-Commit-Position: refs/heads/master@{#384134} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: d6e658265a6a3baa7cd7befecb24b12acb181047