tree bf873ffeca2738802977839255cbcc87933b17aa
parent 21814e71db756f39b69fb1a3e06350fa555a79b1
author Damien Neil <dneil@google.com> 1695271687 -0700
committer Damien Neil <dneil@google.com> 1696355924 +0000

quic: correctly extend peer's flow control window after MAX_DATA

When sending the peer a connection-level flow control update in
a MAX_DATA frame, we weren't recording the updated limit locally.
When the peer wrote data past the old limit, we would incorrectly
close the connection with a FLOW_CONTROL_ERROR.

For golang/go#58547

Change-Id: I6879c0cccc3cfdc673b613a07b038138d9e285ff
Reviewed-on: https://go-review.googlesource.com/c/net/+/530075
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Jonathan Amsterdam <jba@google.com>