Home/Docs/Windows Guide/Use cases and recipes (Windows)

Windows Guide

Use cases and recipes (Windows)

Worked examples for ProxyBridge on Windows: route a browser through Burp Suite, intercept a desktop app that ignores proxy settings, route one site, split traffic between proxies, block an app, proxy UDP, and watch what a program connects to.

Use cases and recipes

Each recipe lists exactly what to enter. They assume you have read the quick start; the field names are explained in Proxy servers and Proxy rules.

Only test applications, devices and networks you own or have written permission to test.

1. Send a browser through Burp Suite, ZAP or mitmproxy

Goal: all of Chrome's and Edge's web traffic goes through an HTTP proxy listener on your PC, without changing the browser's proxy setting.

  1. Start the tool's proxy listener, for example Burp Suite on 127.0.0.1:8080.
  2. Proxy > Proxy Settings... > Add...: Name Burp, Address 127.0.0.1, Port 8080, Protocol HTTP.
  3. Proxy > Proxy Rules... > Add...:
Field Value
Name Browser to Burp
Applications chrome.exe; msedge.exe
Target Hosts *
Target Ports *
Protocol TCP
Action Burp
  1. Open a site in the browser. In the Connections tab you should see chrome.exe ... via Proxy HTTP://127.0.0.1:8080.
  2. For HTTPS, install the tool's CA certificate in Windows, as you would for any intercepting proxy.

Browsers and QUIC. Chrome and Edge try HTTP/3 (QUIC, over UDP) first. A rule with Protocol TCP leaves that UDP traffic alone, and the browser falls back to normal HTTPS over TCP, which is what an HTTP proxy can see. If a site keeps using QUIC, switch HTTP/3 off with the browser flag chrome://flags/#enable-quic.

2. Intercept a desktop application that has no proxy setting

Goal: see the traffic of a program (a game launcher, a vendor tool, a thick client) that ignores both its own and Windows' proxy settings.

  1. Find the program name: start it, open Proxy > Proxy Rules... > Add..., click Running... and pick it from the list (or type its .exe name).
  2. Add a proxy that understands the traffic. For non-HTTP protocols use a SOCKS5 proxy (see Use with security tools).
  3. Rule: Applications the-app.exe, hosts *, ports *, Protocol Both (TCP + UDP), Action your proxy.
  4. If the program also talks to a helper on your own PC (127.0.0.1) and you want that too, tick Also proxy localhost traffic, with the proxy on the same PC.
  5. Restart the program (connections that were already open keep their old route) and watch the Live Connections tab.

If the program uses several executables (a launcher plus helper processes), add them all in the Applications field, separated by ;. The Running... window lets you tick several at once.

3. Route one site or one domain

Goal: only traffic to github.com and its sub-domains uses the proxy. The rest of the browser goes directly.

Field Value
Applications chrome.exe
Target Hosts github.com; *.github.com
Target Ports 443
Protocol TCP
Action your proxy

Domain rules need plain DNS. If the browser uses Secure DNS (DNS over HTTPS), turn it off for this to work, or use IP addresses in Target Hosts instead. See domain names need plain DNS.

4. Send only the company network through the corporate proxy

Goal: internal addresses and names go through the company proxy. Everything else is direct.

Field Value
Applications *
Target Hosts 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; *.corp.example.com
Target Ports *
Protocol Both (TCP + UDP)
Action the corporate proxy

Everything that does not match goes out directly. The same networks can also be written as wildcards (10.*.*.*) or as ranges (172.16.0.0-172.31.255.255). CIDR notation needs version 4.3.0 or later; on older versions use the wildcard or range form.

5. Different programs, different proxies

Goal: chrome.exe through a local Burp listener, curl.exe and python.exe through a remote SOCKS5 proxy, at the same time.

  1. Add two proxy servers: Burp (HTTP, 127.0.0.1:8080) and Remote (SOCKS5, proxy.example.com:1080, with login if needed).
  2. Rule 1: Applications chrome.exe, Action Burp.
  3. Rule 2: Applications curl.exe; python.exe, Action Remote.

The Rule : Proxy column in Live Connections shows which rule and proxy each connection used.

6. Make a command-line tool use a proxy

Many tools (curl, git, pip, npm, wget, your own scripts) do not read the Windows proxy setting, and each uses its own environment variable or flag. One rule covers them all:

Field Value
Applications curl.exe; git.exe; pip.exe; python.exe; node.exe
Action your proxy

Because rules match by program name, the tool does not need to know about the proxy.

7. Block a program

Goal: an updater or telemetry tool must not reach the network.

Field Value
Applications updater.exe
Target Hosts *
Protocol Both (TCP + UDP)
Action Block

To allow only one server and block everything else for the same program, use two rules in this order:

Order Applications Target Hosts Action
1 app.exe api.example.com Direct
2 app.exe * Block

The first matching rule wins, so connections to api.example.com are allowed and everything else from app.exe is blocked.

8. Proxy UDP (games, voice, QUIC)

Goal: send a program's UDP traffic through a SOCKS5 proxy.

  1. Use a SOCKS5 proxy that supports UDP ASSOCIATE. Test it in the Proxy Checker: Test 4: SOCKS5 UDP ASSOCIATE support must pass. (Nexus Proxy is a SOCKS5 server built to test UDP, HTTP/3 and QUIC with ProxyBridge.)
  2. Rule: Applications game.exe, hosts *, ports *, Protocol UDP (or Both), Action the SOCKS5 proxy.
  3. Check Live Connections: the flows appear with the protocol UDP.

An HTTP proxy cannot carry UDP. See UDP, QUIC and HTTP/3.

9. See what a program connects to, without any proxy

Goal: find out which servers an unknown program talks to.

You do not need a rule. The Connections tab lists connections from every program on the PC, with via Direct for the ones no rule affects.

  1. Start the program.
  2. In the Connections tab, type its name in the search box and press Enter.
  3. Tick Settings > Log Every Connection if you want every single connection instead of one line per destination.

To hide the noise from other programs, add an Include log filter for the program.

10. See an application as it looks from another place

Goal: check how a service or site behaves when your application's requests come from your proxy's network location, for example a staging network or a test region.

Add the proxy that sits in that network, then add a rule for the application (or the browser) with that proxy as the action. The destination sees the proxy's address instead of yours, and your other programs are unaffected.

11. Keep several setups apart

Make one profile per task: burp-web, mitm-mobile-backend, office. Switch with Profile > Switch Profile. Export the profile and import it on another PC to repeat the setup.

12. Temporarily turn everything off

Untick Proxy > Enable ProxyBridge (or the same item in the tray menu). New connections go out directly, even those that matched a Block rule, until you tick it again. See pausing.