commit | 4e3e65776a613132d628ca7d2be7571cb26f37c4 | [log] [tgz] |
---|---|---|
author | dschinazi <dschinazi@google.com> | Fri Aug 02 12:57:17 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Aug 02 16:18:42 2019 -0700 |
tree | 87b888b962cb5c04ff69ab61248250098d66a10a | |
parent | 43eefae7ff3b3a723826fff477120c40733c6d76 [diff] |
Send correct stateless reset token when using TLS When using TLS, the stateless reset token needs to be populated in the QuicConfig early in the session's lifetime to ensure it's correctly encoded in the server's transport parameters. Previously the server would send an all-zeroes token. I've confirmed that EndToEndTestWithTls.SendStatelessResetTokenInShlo fails without the fix and passes with the fix. gfe-relnote: send correct reset token, protected by disabled TLS flag PiperOrigin-RevId: 261374750 Change-Id: I60725c5eb6cedfa1b06cf3797bf258875fb495eb
QUICHE (QUIC, Http/2, Etc) is Google‘s implementation of QUIC and related protocols. It powers Chromium as well as Google’s QUIC servers and some other projects.
The code is currently in process of being moved from https://cs.chromium.org/chromium/src/net/third_party/ into this repository. Please excuse our appearance while we're under construction.