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
diff --git a/quic/core/tls_client_handshaker.cc b/quic/core/tls_client_handshaker.cc
index 46bf285..fa19005 100644
--- a/quic/core/tls_client_handshaker.cc
+++ b/quic/core/tls_client_handshaker.cc
@@ -295,6 +295,10 @@
return SSL_early_data_accepted(ssl()) == 1;
}
+ssl_early_data_reason_t TlsClientHandshaker::EarlyDataReason() const {
+ return SSL_get_early_data_reason(ssl());
+}
+
bool TlsClientHandshaker::ReceivedInchoateReject() const {
QUIC_BUG_IF(!one_rtt_keys_available_);
// REJ messages are a QUIC crypto feature, so TLS always returns false.
