feat: implement TLS fingerprint spoofing via wreq-js#137
Open
LinearSakana wants to merge 2 commits intodecolua:masterfrom
Open
feat: implement TLS fingerprint spoofing via wreq-js#137LinearSakana wants to merge 2 commits intodecolua:masterfrom
LinearSakana wants to merge 2 commits intodecolua:masterfrom
Conversation
added 2 commits
February 16, 2026 15:41
…proxy * Add `TlsClient` utility to mimic Chrome 124 TLS handshake * Update `patchedFetch` to use TLS client when no proxy is configured * Add fallback mechanism to native fetch on TLS client failure * Add `wreq-js` dependency to package.json
* Offload proxy configuration to `wreq-js` session in `tlsClient` * Remove manual proxy agent management and dependencies in `proxyFetch` * Remove redundant `ResponseWrapper` and `HeadersCompat` classes * Implement `NO_PROXY` support to bypass TLS client when needed
diegosouzapw
added a commit
to diegosouzapw/OmniRoute
that referenced
this pull request
Feb 16, 2026
- Add TlsClient module (Chrome 124 fingerprint via wreq-js) - Integrate TLS client as opt-in layer in proxyFetch.js (ENABLE_TLS_FINGERPRINT) - Add per-request TLS tracking via AsyncLocalStorage - Add TLS fingerprint column and badge to Proxy Logger dashboard - Add TLS Fingerprint section to ProxyLogDetail modal - Add wreq-js dependency - Document ENABLE_TLS_FINGERPRINT in .env.example Adapted from upstream PR decolua/9router#137, preserving all OmniRoute-specific proxy features (AsyncLocalStorage context, proxyDispatcher, SOCKS5, Symbol-based patch state).
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.
Summary
To address the increasingly strict ban measures imposed by Google on Antigravity reverse proxies, this PR implements TLS fingerprint spoofing. By mimicking legitimate Chrome 124 TLS fingerprints, this change MAY reduce the risk of detection and improve the stability of the proxy service.
This implementation is inspired by the technique used in antigravity-claude-proxy but includes additional enhancements for better compatibility.
Key Changes
1. New TLS Client Module (
open-sse/utils/tlsClient.js)TlsClientusingwreq-jsto create TLS sessions with Chrome 124 on macOS fingerprints.HTTPS_PROXY/HTTP_PROXY/ALL_PROXYenv vars).2. Global Fetch Integration (
open-sse/utils/proxyFetch.js)proxyFetch.jsto route traffic through theTlsClientby default.wreq-jsnow handles both TLS spoofing and proxy tunneling natively.NO_PROXYbypass logic for local/internal traffic.fetchif the TLS client encounters critical errors.Impact
Testing
npm installand build process.wreq-jssession.