NW.js Proxy Settings Differ Between Chromium and Node Requests
Configure NW.js web-engine proxy rules separately from Node libraries used by the same desktop application.
NW.js can load a DOM image and fetch JSON through a Node library in the same window. Identify the call creating the request before selecting a proxy interface.
For the documented web-engine path:
nw.App.setProxyConfig('proxy.example:8080', '');
const route = nw.App.getProxyForURL('https://www.example.com/');The first argument is the proxy rule and the second the PAC URL. This selects a fixed HTTP endpoint for destination schemes with PAC empty; HTTPS uses its supported tunnel path. In an independent public-page test without proxy authentication, an entry from the HTTP proxy list can replace that endpoint.
| Request producer | Policy to inspect |
|---|---|
| DOM resource or browser fetch | NW.js web-engine proxy configuration |
| Node core HTTP or a package-owned transport | The agent or public proxy interface of that client |
getProxyForURL returns PAC-style policy text for a DOM load, such as PROXY plus an endpoint or DIRECT. It does not confirm that a completed request used it.
Changing process.env.http_proxy does not make every implementation read the variable. Label diagnostics with the producer/client name and its outcome. Use that package's public configuration rather than patching node_modules files that an upgrade replaces. For Node core HTTPS calls using SOCKS, one such interface is a SOCKS-capable HTTPS agent.