New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default-tls reqwest feature necessary? #111
Comments
The TLS configuration of the client followed the TLS configuration of reqwest, but it looks like this changed in seanmonstar/reqwest#749.
Looking at https://github.com/seanmonstar/reqwest/blame/71386d8734f7904e48e4b3238f918eaecdabe7f3/Cargo.toml#L30, it looks like reqwest's I think we want support for TLS by default. If I understand the issue correctly, if [features]
default = ["native-tls"]
# optional TLS
native-tls = ["reqwest/native-tls"]
rustls-tls = ["reqwest/rustls-tls"]
[dependencies]
reqwest = { version = "~0.10", default-features = false, features = ["default-tls", "gzip", "json"] } is changed to [features]
default = ["native-tls"]
# optional TLS
native-tls = ["reqwest/native-tls"]
rustls-tls = ["reqwest/rustls-tls"]
[dependencies]
reqwest = { version = "~0.10", default-features = false, features = ["gzip", "json"] } Then [dependencies]
elasticsearch = { version = "*", default-features = false, features = ["rustls-tls"] } should not pull in |
Yep, I think you are correct, we should change it to:
I can open a PR to do that tomorrow... |
Closing as #115 is merged |
I spent a bit of time figuring out why my static musl binary required
openssl
even though all of my dependencies that usereqwest
use therustls-tls
feature and disabled the default feature.I think I traced it to
elasticsearch
adding thedefault-tls
feature, which brings inhyper-tls
, which brings innative-tls
, which depends onopenssl
(on linux) :/TL;DR: Do we need the
default-tls
feature?The text was updated successfully, but these errors were encountered: