back to home

0x676e67 / wreq

An ergonomic Rust HTTP Client with TLS fingerprint

View on GitHub
702 stars
90 forks
9 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing 0x676e67/wreq in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/0x676e67/wreq)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

wreq > 🚀 Help me work seamlessly with open source sharing by sponsoring me on GitHub An ergonomic and modular Rust HTTP client for advanced and low-level emulation, with customizable TLS, JA3/JA4, and HTTP/2 fingerprinting capabilities. Features • Plain bodies, JSON, urlencoded, multipart • HTTP Trailer • Cookie Store • Redirect Policy • Original Header • Rotating Proxies • Tower Middleware • WebSocket Upgrade • HTTPS via BoringSSL • HTTP/2 over TLS Emulation • Certificate Store (CAs & mTLS) Example The following example uses the Tokio runtime with optional features enabled by adding this to your : And then the code: Behavior • **HTTP/1 over TLS** In the Rust ecosystem, most HTTP clients rely on the http library, which performs well but does not preserve header case. This causes some **WAFs** to reject **HTTP/1** requests with lowercase headers (see discussion). **wreq** addresses this by fully supporting **HTTP/1** header case sensitivity. • **HTTP/2 over TLS** Due to the complexity of **TLS** encryption and the widespread adoption of **HTTP/2**, browser fingerprints such as **JA3**, **JA4**, and **Akamai** cannot be reliably emulated using simple fingerprint strings. Instead of parsing and emulating these string-based fingerprints, **wreq** provides fine-grained control over **TLS** and **HTTP/2** extensions and settings for precise browser behavior emulation. • **Device Emulation** **TLS** and **HTTP/2** fingerprints are often identical across various browser models because these underlying protocols evolve slower than browser release cycles. **100+ browser device emulation profiles** are maintained in wreq-util. Building Compiling alongside **openssl-sys** can cause symbol conflicts with **boringssl** that lead to link failures, and on **Linux** and **Android** this can be avoided by enabling the ** ** feature. Install BoringSSL build dependencies and build with: This GitHub Actions workflow can be used to compile the project on **Linux**, **Windows**, and **macOS**. Services Help sustain the ongoing development of this open-source project by reaching out for commercial support. Receive private guidance, expert reviews, or direct access to the maintainer, with personalized technical assistance tailored to your needs. License Licensed under either of Apache License, Version 2.0 (LICENSE or http://www.apache.org/licenses/LICENSE-2.0). 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. Sponsors **Solve reCAPTCHA in less than 2 seconds** **Captcha.fun** delivers fast, reliable CAPTCHA solving built for automation at scale. With simple API integration, consistent performance, and competitive pricing, it's an easy way to keep your workflows moving without delays—use code ** ** for **10% bonus credits**. **Dashboard** | **Docs** | **Discord** --- TLS fingerprinting alone isn't enough for modern bot protection. **Hyper Solutions** provides the missing piece - API endpoints that generate valid antibot tokens for: **Akamai** • **DataDome** • **Kasada** • **Incapsula** No browser automation. Just simple API calls that return the exact cookies and headers these systems require. **Dashboard** | **Docs** | **Discord** Accolades A hard fork of reqwest.