Chain ZAP Through the Corporate Forward Proxy

browser → ZAP local listener → corporate proxy → destination

Keep the browser pointed at ZAP's local listener. In ZAP Options → Network → Connection, enable the HTTP Proxy section and enter the corporate host/port and required authentication.

Check competing settings before judging those fields ineffective. ZAP's documented outgoing SOCKS proxy takes precedence when both are configured. Exclusions can also send intranet/local targets another route.

For NTLM, the outgoing proxy options include domain and an NTLMv2 choice. Use the operator's account format. ZAP can retain the password only for the session rather than persist it.

Verify the actual failing destination and stage. Browser-to-ZAP reachability proves only the first hop; ZAP opens its own onward connection. Distinguish a corporate challenge from a destination response rather than relying on the browser's independent ability to browse.