Unified Headless Chrome Accepts --no-proxy-server
Apply no-proxy-server to current unified headless Chrome rather than carrying legacy headless workarounds forward.
Unified headless Chrome shares the ordinary Chrome implementation. Use its documented --no-proxy-server switch for a direct request:
google-chrome --headless --no-proxy-server \
--dump-dom https://example.net/Start the intended Chrome binary in a process that owns these flags. Sending a command to an already running instance does not establish that it adopted a new proxy policy.
Chrome introduced unified headless in version 112. Historical reports about the separate headless implementation need that version context; chrome-headless-shell remains a different executable.
If direct access still fails, keep the actual browser version and connection error with the diagnosis. The direct switch chooses a route; that route still needs to reach the destination.