Update reqwest #104
Merged
Update reqwest #104
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updates
reqwestto 0.13.reqwesthas now changed the default TLS backend fromnative-tls(bad) torustls(good), but defaults crypto toaws-lc-rs(bad) instead ofring(good). I despiseaws-lc-rsand would never wish to force it on end users, so this change also means thattame-indexnow takes a hands off approach to TLS entirely. This increases the burden on the end user to properly configure theirClientbefore passing it totame-index, which is unfortunate, but should be healthier in the long run.I've added a tls.rs example using webpki-roots with rustls. End users who wish to use aws-lc-rs, or native-tls, can figure that out themselves.