This repository has been archived by the owner on Nov 13, 2021. It is now read-only.
Use hyper native tls #123
Merged
Use hyper native tls #123
Conversation
This file contains 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
added 2 commits
May 14, 2017 15:48
as of hyper 0.10 it doesn't ship with a native tls implementation anymore and has to be installed and configured separately.
|
bors try |
Build succeeded |
badboy
approved these changes
Jul 4, 2017
|
bors r+ |
not-a-robot bot
added a commit
that referenced
this pull request
Jul 4, 2017
123: Use hyper native tls r=badboy Resolves #122 and based on #118 This fixes the problem described in #122 that GitHub rejects pushes performed over http. This is caused by hyper which does not ship with its own tls implementation anymore. We fix this by including `hyper-native-tls` and configuring out GitHub client explicitly to use https.
Build succeeded |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #122 and based on #118
This fixes the problem described in #122 that GitHub rejects pushes performed over http. This is caused by hyper which does not ship with its own tls implementation anymore. We fix this by including
hyper-native-tlsand configuring out GitHub client explicitly to use https.