dsh-network-config

LIMITATIONS

Known limitations

- **No SOCKS and no PAC.** The transport accepts `http(s)://` proxy URLs only. A system configured with a PAC script (`AutoConfigURL`) is reported and treated as direct rather than pretending to work. - **`proxyRouteFor()` uses the package's narrower matcher.** Because the official policy is installed as-is, `dsh-web-fetch-http` decides whether to *fetch* through the proxy with that matcher — so fetching an **intranet** URL can still be routed through the proxy. Public fetches are unaffected. Traffic (models, search, MCP) goes through this plugin's matcher. - **Child processes follow the policy only on Node 22.21+/24+.** That is `dsh-http-proxy`'s documented behaviour, driven by `NODE_USE_ENV_PROXY`. In *Direct* mode the plugin additionally clears `all_proxy`/`ALL_PROXY` so children do not keep using one. - **Needs `undici` resolvable from inside the profile.** Without it the plugin falls back to the package's dispatcher and says so in the page — usable, but wildcard entries and private-address bypass stop applying. - **Exclusive with other proxy plugins.** Whoever calls `setGlobalDispatcher` last wins; do not run this alongside e.g. `dsh-clash-proxy`. - **System proxy discovery is Windows-only**; other platforms fall back to the environment.