dsh-plugin-proxy-env

LIMITATIONS

Known limitations

- **It covers process environment, not `web_fetch`.** DSH's `web_fetch` pins connections with a custom undici `Agent` (SSRF / DNS-rebinding defence) and bypasses the global dispatcher by design, so it will not use the proxy even when everything else does. For blocked sites use a cloud-based page reader, or have the agent fetch with `node` / `python` from a shell. - **Registry reading shells out to `reg.exe`**, with stdout redirected to a temp file rather than a pipe (pipes fail with EPERM inside restricted-token sandboxes). When unreadable it falls back to an exported `HTTPS_PROXY` / `HTTP_PROXY`. - **Non-Windows** hosts use configuration and environment variables only. - **`patchGlobalDispatcher` is a runtime switch**: it needs `undici` to resolve and a version that ships `EnvHttpProxyAgent` (the only variant that honours `NO_PROXY`). Otherwise it is skipped and logged.