Feature Request: Optional Traffic Obfuscation Layer for DPI-Restricted Networks

[msksrv]

Hello,

First of all, thank you for providing and maintaining the official WhatsApp Proxy project. It is an important tool for maintaining connectivity in restricted network environments.

I would like to propose a feature request: adding an optional traffic obfuscation layer for deployments in countries where aggressive DPI (Deep Packet Inspection) is used.

Currently, the proxy relies on standard TLS over ports 80/443/5222. While this works in many environments, in some regions DPI systems perform traffic fingerprinting and detect WhatsApp proxy patterns even when running over HTTPS on port 443.

Possible enhancements could include:

Optional TLS fingerprint randomization

Packet padding / traffic shaping to reduce protocol distinguishability

Support for configurable TLS profiles

Optional fronting / multiplexing mode behind standard HTTPS services

An officially supported “stealth mode” optimized for restrictive networks

The goal would not be to bypass lawful restrictions, but to improve resilience in environments where encrypted traffic is aggressively filtered or fingerprinted.

Even an experimental or configurable obfuscation mode would significantly improve reliability in DPI-heavy regions.

Thank you for considering this suggestion.