fix(transport
): use HttpsConnector
in HyperTransport
#1899
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.
Motivation
Currently the
HyperTransport
uses theHttpConnector
as the default connector making it impossible to use:ProviderBuilder::new().on_builtin("https://..")
when thehyper
feature is enabled as it will always throw "invalid URL, scheme is not http".Solution
Use
HttpsConnector
from thehyper_tls
lib as default inHyperTransport
.PR Checklist