wreq 0.15.3

A blazing-fast Rust HTTP Client with TLS fingerprint
Documentation

wreq

CI Crates.io License Crates.io MSRV crates.io Crates.io Total Downloads

An ergonomic all-in-one HTTP client for browser emulation with TLS, JA3/JA4, and HTTP/2 fingerprints.

Version migration: wreq 0.15.3 replaces wreq 5.3.0 under the new versioning policy. Cargo will not migrate existing 5.x requirements automatically, so update them to wreq = "0.15". The 6.0.0-rc line is frozen. The next release will be the stable 0.16.0.

Features

  • Plain bodies, JSON, urlencoded, multipart
  • Cookie Store
  • Header Order
  • Redirect Policy
  • Rotating Proxies
  • Certificate Store
  • WebSocket Upgrade
  • HTTPS via BoringSSL
  • HTTP/2 over TLS Emulation

Example

This asynchronous example utilizes Tokio with optional features enabled, requiring the following configuration in Cargo.toml:

[dependencies]
tokio = { version = "1", features = ["full"] }
wreq = "0.15"
wreq-util = "0.1"

And then the code:

use wreq::Client;
use wreq_util::Emulation;

#[tokio::main]
async fn main() -> Result<(), wreq::Error> {
    // Build a client
    let client = Client::builder()
        .emulation(Emulation::Firefox136)
        .build()?;

    // Use the API you're already familiar with
    let resp = client.get("https://tls.peet.ws/api/all").send().await?;
    println!("{}", resp.text().await?);

    Ok(())
}

Emulation

  • HTTP/2 over TLS

    JA3/JA4/Akamai fingerprints cannot accurately simulate browser fingerprints due to the sophistication of TLS encryption and the popularity of HTTP/2. wreq does not plan to support parsing these fingerprint strings for simulation. Users are encouraged to customize the configuration according to their own needs.

Building

Avoid compiling with packages that depend on openssl-sys, as it shares the same prefix symbol with boring-sys, potentially leading to link failures and other issues. Even if compilation succeeds, using both openssl-sys and boring-sys together can result in memory segmentation faults. Until the upstream Boring resolves these linking conflicts, using rustls is the best workaround.

Install the dependencies required to build BoringSSL

sudo apt-get install build-essential cmake perl pkg-config libclang-dev musl-tools -y

cargo build --release

This GitHub Actions workflow can be used to compile the project on Linux, Windows, and macOS.

License

Released under the Apache-2.0 License.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed as above, without any additional terms or conditions.

Accolades

The project is based on a fork of reqwest.