Headless browser proxy settings not working in v1.4.0 (worked in v1.3.0)

[c1phy]

Hi team,

there seems to be a regression in katana v1.4.0 related to proxy settings when using the headless browser.

In v1.3.0, the headless browser correctly respects the proxy configuration and routes traffic through the proxy (e.g. Burp Suite).
In v1.4.0, the same command no longer sends any traffic to the configured proxy server.

---

Command used

katana -u https://example.com -headless -headless-options --disable-gpu,proxy-server=http://127.0.0.1:8080 -ct 2

Expected behavior

All headless browser traffic should be routed through the specified proxy (http://127.0.0.1:8080), as it does in v1.3.0.

Actual behavior

In v1.4.0, no traffic reaches the proxy server at all.
The proxy configuration appears to be ignored.

Thanks and Best
c1phy

[bad-antics]

This looks like a regression in how v1.4.0 handles proxy settings for the headless Chrome instance.

Workaround until fixed:

1. Set proxy via environment variable (Chrome respects this):

export HTTPS_PROXY=http://127.0.0.1:8080
export HTTP_PROXY=http://127.0.0.1:8080
katana -u https://target.com -headless

2. Use system-wide proxy with proxychains:

proxychains katana -u https://target.com -headless -proxy http://127.0.0.1:8080

3. Pin to v1.3.0 until the fix ships:

go install github.com/projectdiscovery/katana/cmd/katana@v1.3.0

Root cause likely: In v1.4.0, the headless browser initialization may have changed how Chrome DevTools Protocol handles proxy flags. The --proxy-server flag needs to be passed to the Chrome launch args, which may have been dropped.

I'd recommend also filing this as a bug report (not just discussion) so it gets tracked for a patch release — this is a clear regression since it worked in v1.3.0.

[dogancanbakir]

Tracking at #1535