-
Notifications
You must be signed in to change notification settings - Fork 49
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
Reorganize feature flags to separate out different tls implementations #54
Comments
Edit: Surf would require that but http-client doesn't. |
Fishrock123
added a commit
to Fishrock123/http-client
that referenced
this issue
Feb 11, 2021
A successor to http-rs#53, this separates out the tls feature flags, which should be nicer. Fixes: http-rs#54
Fishrock123
added a commit
to Fishrock123/http-client
that referenced
this issue
Feb 12, 2021
A successor to http-rs#53, this separates out the tls feature flags, which should be nicer. Fixes: http-rs#54
Fishrock123
added a commit
to Fishrock123/http-client
that referenced
this issue
Feb 12, 2021
A successor to http-rs#53, this separates out the tls feature flags, which should be nicer. Fixes: http-rs#54
Fishrock123
added a commit
to Fishrock123/http-client
that referenced
this issue
Feb 12, 2021
A successor to http-rs#53, this separates out the tls feature flags, which should be nicer. Fixes: http-rs#54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #53
I think Ideally it would be like to feature flags for the async-h1 client:
h1-client
andnative-tls
orrustls
.This should be acceptable because by the time of the next major, it seems likely we may be switching to using async-h1 by default anyways: http-rs/surf#223 (comment)
The text was updated successfully, but these errors were encountered: