okhttp: fix incorrect connection-level flow control handling at beginning of connection (v1.28.x backport) #6777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specifically, this addresses bugs that occur when the
OkHttpChannelBuilder.flowControlWindow(int)
setting is increased from its default value.Two changes:
OkHttpChannelBuilder.flowControlWindow(int)
is sent via Settings.INITIAL_WINDOW_SIZE. Also send a WINDOW_UPDATE after Settings to update the connection-level window.OutboundFlowController
with an initialWindowSize of 65335 bytes per the http2 spec instead of using the inbound window size.Fixes #6685
Backport of #6742.