Commit 350aad2
committed
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>1 parent 21814e7 commit 350aad2Copy full SHA for 350aad2
File tree
Expand file treeCollapse file tree
2 files changed
+11
-0
lines changedOpen diff view settings
Filter options
- internal/quic
Expand file treeCollapse file tree
2 files changed
+11
-0
lines changedOpen diff view settings
Collapse file
+1Lines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| ||
106 | 106 | |
107 | 107 | |
108 | 108 | |
| 109 | + |
109 | 110 | |
110 | 111 | |
111 | 112 | |
|
Collapse file
internal/quic/conn_flow_test.go
Copy file name to clipboardExpand all lines: internal/quic/conn_flow_test.go+10Lines changed: 10 additions & 0 deletions
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| ||
35 | 35 | |
36 | 36 | |
37 | 37 | |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | + |
38 | 48 | |
39 | 49 | |
40 | 50 | |
|
0 commit comments