Support local vs remote flow control with TLS, and fix initial limits
This CL fixes a bug found during interop testing where we were failing to communicate with clients that do not send initial_max_stream_data_bidi_local. (When sent by clients, this is the transport parameter that governs the server-initiated streams which are not used by HTTP/3.) All of our tests sent the same value for _local and _remote so we did not notice that we had them backwards. This CL fixes the issue and adds tests to prevent regressions. This CL also fixes an issue where the initial limits were incorrectly set for versions that AllowsLowFlowControlLimits().
gfe-relnote: change QUIC flow control transport parameters, protected by disabled TLS flag.
PiperOrigin-RevId: 273843552
Change-Id: Id8bb3a59029ee9442ebf163fd658f38c47024950
diff --git a/quic/core/quic_session.h b/quic/core/quic_session.h
index 1805387..59b3ee2 100644
--- a/quic/core/quic_session.h
+++ b/quic/core/quic_session.h
@@ -605,6 +605,20 @@
// control window in a negotiated config. Closes the connection if invalid.
void OnNewStreamFlowControlWindow(QuicStreamOffset new_window);
+ // Called in OnConfigNegotiated when we receive a new unidirectional stream
+ // flow control window in a negotiated config.
+ void OnNewStreamUnidirectionalFlowControlWindow(QuicStreamOffset new_window);
+
+ // Called in OnConfigNegotiated when we receive a new outgoing bidirectional
+ // stream flow control window in a negotiated config.
+ void OnNewStreamOutgoingBidirectionalFlowControlWindow(
+ QuicStreamOffset new_window);
+
+ // Called in OnConfigNegotiated when we receive a new incoming bidirectional
+ // stream flow control window in a negotiated config.
+ void OnNewStreamIncomingBidirectionalFlowControlWindow(
+ QuicStreamOffset new_window);
+
// Called in OnConfigNegotiated when we receive a new connection level flow
// control window in a negotiated config. Closes the connection if invalid.
void OnNewSessionFlowControlWindow(QuicStreamOffset new_window);
