commit 786a4abc079afc6e7080f9df6b365308597b5f0d
author nharper <nharper@google.com> Fri Jul 10 11:56:01 2020 -0700
committer Copybara-Service <copybara-worker@google.com> Fri Jul 10 11:56:33 2020 -0700
tree 949eaeeca0a0a3efdb6f62712dabd5577fe8c4bf
parent 820312778359a1930a285ed31837f2b4d21fdbf2

Only set QUIC TLS 0-RTT client state if a 0-RTT handshake was attempted

Even if an SSL_SESSION is early data capable, it is still possible (for
various reasons) that BoringSSL will decide not to do a 0-RTT handshake.
TlsClientHandshaker should wait for a signal from BoringSSL that it is
attempting a 0-RTT handshake before it sets saved transport and application
state for early data.

Client-side only quic behavior change, not flag protected.

PiperOrigin-RevId: 320646436
Change-Id: Ib1cfe2640d3cd62e23344ede852b91756a44f687