Add wreq-ruby to FFI / Ruby section#78
Merged
Merged
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
2 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.
wreq-ruby is the first production-ready Ruby HTTP client with real browser TLS/HTTP2 fingerprinting — and it's powered by Rust.
Ruby has never had a library capable of emulating browser TLS and HTTP2 fingerprints. Every existing Ruby HTTP library relies on OpenSSL, which provides no control over TLS extension ordering, cipher suite ordering, or HTTP/2 frame settings. Python, Go, and Node have had solutions for this. Thanks to the wreq crate (403k+ downloads), Ruby now does too.
wreq-ruby wraps the wreq crate via FFI with pre-compiled native gems for Linux and macOS, so Ruby developers don't need a Rust toolchain. It's used in production at SearchApi and actively maintained.