I built an HTTP client that perfectly mimics Chrome 142
BoringSSL and nghttp2. Matches JA3N, JA4, and JA4_R fingerprints. Supports HTTP/2, async/await, and works with Cloudflare-protected sites. Not trying to compete with curl_cffi - just a learning project that turned into something functional.
In plain words
This HTTP client mimics Chrome 142's behavior using BoringSSL and nghttp2, matching JA3N, JA4, and JA4_R fingerprints to avoid detection. It supports HTTP/2, async/await syntax, and handles Cloudflare-protected sites. Designed for developers who need requests that appear identical to Chrome traffic, the tool combines browser-level fingerprinting with modern async programming patterns.
written from the facts on this page · September 2026
More work this month
the category →


The app store for voice native apps that lives in your notch
Work · 28d ago · voiceos.com

The New Calendly▲211Handle all of the work before, during, and after meetings
Work · 17d ago · calendly.com
Launched alongside, November 2025
the whole month →
- IB
Life & fun · Nov 2025 · bitsnpieces.dev



- BBoing▲782
Life & fun · Nov 2025 · boing.greg.technology