Auto-port 4.1: HTTP2: Ensure HTTP2 preface is always send as first message#16642
Merged
Conversation
Motivation: We had a race in which it was possible that we send another frame before the preface if the write happened in the ChannelListener attached to the connect promise. Modifications: - Ensure we always send the preface before we give the user a chance to write another frame. - Add unit test Result: Fixes #16635 (cherry picked from commit caf6f41)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Auto-port of #16636 to 4.1
Cherry-picked commit: caf6f41
Motivation:
We had a race in which it was possible that we send another frame before the preface if the write happened in the ChannelListener attached to the connect promise.
Modifications:
Result:
Fixes #16635