-
Notifications
You must be signed in to change notification settings - Fork 121
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
Please make TLS support optional #219
Comments
I'd like to take a swing at this and submit a PR if it would be accepted. |
Needs support in http-client. We should support this. |
@brightly-salty are you still interested in this? I think that the |
Sure @Fishrock123 , sorry about that, must've slipped my mind. I'd be happy to work on it, I think it's just making a feature flag and configuring the tls-using code based on that? |
I think it would mostly need to be an alternate feature flag on Surf, probably something like |
Sometimes, I only need http support, not https; for instance, the instance metadata services in cloud environments only need http. For such cases, I would like to be able to use surf with the async-h1 backend and no TLS stack.
The text was updated successfully, but these errors were encountered: