commit 26e3e88cef291cc283d31dff7c5b51338aef5e8d
author nharper <nharper@google.com> Wed Sep 09 12:30:55 2020 -0700
committer Copybara-Service <copybara-worker@google.com> Wed Sep 09 12:31:27 2020 -0700
tree be65f6e89ef96145ba76376287f649efcfb9527b
parent 7f547143b82d4ea8fc34161a0c014f655449c1f5

Add method to get reason why 0-RTT was accepted or rejected in QUIC

This provides additional detail compared to
QuicCryptoClientStreamBase::EarlyDataAccepted to indicate why early data was
rejected (if it was). This change only adds client-side logging information
- it doesn't change the behavior of a client.
PiperOrigin-RevId: 330774692
Change-Id: I9f59ee5a4a64a5617b5ff9de5aba34156b88538f

quic/core/quic_crypto_client_stream.cc

diff --git a/quic/core/quic_crypto_client_stream.cc b/quic/core/quic_crypto_client_stream.cc
index 62a261d..67a9a11 100644
--- a/quic/core/quic_crypto_client_stream.cc
+++ b/quic/core/quic_crypto_client_stream.cc
@@ -71,6 +71,10 @@
   return handshaker_->EarlyDataAccepted();
 }
 
+ssl_early_data_reason_t QuicCryptoClientStream::EarlyDataReason() const {
+  return handshaker_->EarlyDataReason();
+}
+
 bool QuicCryptoClientStream::ReceivedInchoateReject() const {
   return handshaker_->ReceivedInchoateReject();
 }