-
Notifications
You must be signed in to change notification settings - Fork 155
Allow construction with HttpConnector and default ClientConfig #67
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
inikulin
added a commit
to inikulin/hyper-rustls
that referenced
this issue
Apr 1, 2020
inikulin
added a commit
to inikulin/hyper-rustls
that referenced
this issue
Apr 1, 2020
inikulin
added a commit
to inikulin/hyper-rustls
that referenced
this issue
Apr 2, 2020
inikulin
added a commit
to inikulin/hyper-rustls
that referenced
this issue
Apr 17, 2020
inikulin
added a commit
to inikulin/hyper-rustls
that referenced
this issue
Apr 20, 2020
inikulin
added a commit
to inikulin/hyper-rustls
that referenced
this issue
Apr 20, 2020
There's something like that on the main branch now (see #156), you can combine a builder (configuring HTTPS in a consistent and readable way) with a custom connector
|
Based on @g2p's comment above I'm going to close this ticket as resolved. If the updated API doesn't meet the needs of the original poster we can re-open for further discussion. Thanks! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
See for example the example code at hyper-trust-dns.
If I want to supply an
HttpConnector
, for example to change the resolver, it seems that I also have to also supply aClientConfig
.It could be useful to offer a
from(http_connector: T)
which uses the default rustlsClientConfig
.The text was updated successfully, but these errors were encountered: