WPE_CORE_OS // PROXY_MODE
Proxy Mode
Run WPE as a SOCKS proxy server and capture the client's packets there. Use it when Inject Mode does not work, or when you need UDP. Supports port mapping and can be chained into third-party pipelines and licensing systems.
How it works
Proxy Mode intercepts the TCP and UDP traffic marked red in the diagram below.
01How it works · once the SOCKS handshake and authentication are done, the red TCP / UDP traffic is relayed through WPE (Client ↔ WPE ↔ Server).
How to use it
02Option 1 · for desktop and mobile apps that injection cannot reach, or when you need UDP. The built-in Web API lets you plug in a third-party licensing system.
03Option 2 · same as option 1, but some or all ports are forwarded on to Charles for further processing.
04Option 3 · run WPE x64 as an upstream proxy behind CCProxy, when you want CCProxy to handle user management.
Load sharing
05Load sharing · several WPE x64 instances each take a slice of the ports and feed into one CCProxy for distribution — keeps a single machine from stalling and dropping packets at peak.
// TIP
If a desktop app can be hooked directly, Inject Mode is simpler. In Proxy Mode you can use the WPE Proxy Cap client to route traffic in.