Alpn feature #50
Open
Alpn feature #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
Nevermind this doesn't actually do anything ignore this PR. |
Author
|
Actually this does do something since tokio tls re-exports native tls, enabling this feature will make sure the alpn functions get re-exported as well. |
|
May I know if there is any progress here? |
Contributor
|
Sorry, I was only active in this repo for tokio-rustls -- I don't use tokio-native-tls. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Rust native tls 0.2.7 just released and has the capabilities to have do alpn. I have added a feature to tokio native tls to enable alpn support.