Send correct max_ack_delay in QUIC+TLS
This CL fixes a bug where QuicConfig was sending the default value for max_ack_delay instead of the configured vale, when using QUIC+TLS. The only code that sets a non-default value here is either tests or quartc. Quartc is client-only, therefore we do not need flag-protection for this change.
Client-only change
PiperOrigin-RevId: 312164256
Change-Id: Ida7203ca219707d8ac44664c3a3326c215114f1e
diff --git a/quic/core/quic_config.cc b/quic/core/quic_config.cc
index 7c781f4..8cdc121 100644
--- a/quic/core/quic_config.cc
+++ b/quic/core/quic_config.cc
@@ -592,7 +592,7 @@
return max_ack_delay_ms_.SetSendValue(max_ack_delay_ms);
}
-uint32_t QuicConfig::GetMaxAckDelayToToSendMs() const {
+uint32_t QuicConfig::GetMaxAckDelayToSendMs() const {
return max_ack_delay_ms_.GetSendValue();
}
@@ -1110,7 +1110,7 @@
GetMaxUnidirectionalStreamsToSend());
if (GetQuicReloadableFlag(quic_negotiate_ack_delay_time)) {
QUIC_RELOADABLE_FLAG_COUNT_N(quic_negotiate_ack_delay_time, 3, 4);
- params->max_ack_delay.set_value(kDefaultDelayedAckTimeMs);
+ params->max_ack_delay.set_value(GetMaxAckDelayToSendMs());
}
params->ack_delay_exponent.set_value(GetAckDelayExponentToSend());
params->disable_migration =
