[v13] Fix an issue tsh fails when Proxy is in separate mode and web port is TLS-terminated by a load balancer#33407
Merged
greedy52 merged 1 commit intobranch/v13from Oct 12, 2023
Merged
Conversation
…alancer in separate port mode
greedy52
added
backport
no-changelog
rosstimothy
approved these changes
Oct 12, 2023
Joerger
approved these changes
Oct 12, 2023
Merged
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
3 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.
Changelog: none
Backport #33374 to branch/v13
Note that the root cause is introduced in v13. However, since v13 has the fallback mechanism,
tshnever fails like v14 does. So no change log is required for the v13 backport. Still backporting so the new protocol will be successful in this particular scenario without the need for the fallback (performance improvement).