OptionalconnectionFlow-control receive window for each HTTP/2 connection, in bytes.
Bounds in-flight data summed across all sessions multiplexed on one connection (up to 100 streams per connection).
Must be an integer between 65,535 and 2^31 - 1.
OptionalinitialFlow-control receive window for each HTTP/2 stream, in bytes.
Bounds how much data the server can have in flight on a single read session before the client acknowledges it. Raise this to keep high-throughput reads saturated over high-latency links; S2 read batches can be up to 1 MiB each.
Must be an integer between 65,535 and 2^31 - 1.
HTTP/2 flow-control settings for the s2s transport.
Only applies where sessions run over
s2s(HTTP/2); the fetch transport ignores these. Connections are pooled per endpoint, and clients configured with different settings do not share connections.