Add support for setting the TLS configuration name from client connectors in WebSockets Next #48118
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.
This PR adds a
tlsConfigurationName(String)
method to the client connector interfaces, making it possible to specify the TLS configuration at runtime.While writing the tests, I also discovered a bug causing the connector to hang indefinitely on
connectAndAwait()
when a TLS configuration cannot be found. I added appropriate error handling to ensure the underlying exception gets emitted instead of being swallowed by Vert.x, and some test coverage.