tiproxy: fix http tls when only tls cluster is enabled #5555
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.
What problem does this PR solve?
Before, tiproxy will use TLS certs from TiDB to serve both SQL and HTTP ports. When only
tlsCluster
is enabled, there will be errors(others will try to use HTTPS to access tiproxy).Since now we have dedicated
server-http-tls
options, we can now specify certs for tiproxy when onlytlsCluster
is enabled.For backward compatibility, it is also enabled on only
tlsTiDB
, which is wrong. But it is kept for now.Code changes
Tests
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.