[v15] TLS Routing native WebSocket connection upgrade support #38108
Conversation
This file contains 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
* TLS routing connection upgrade using native websocket * update ut in api * lib/web/UT update * fix typo, lint and race * deal with subprotocol negotiation * review comments round 1 * fix lint? * add UT and address some other comments * add env var to toggle mode * fix lint
smallinsky
approved these changes
Feb 13, 2024
|
Friendly ping @strideynet |
strideynet
approved these changes
Feb 26, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
backport of #36343 to branch/v15
changelog: Added TLS routing native WebSocket connection upgrade support
no cherry-pick conflict. not sure why backport bot fails.
working on doc and will backport separately