Update "Use Dev Proxy with Node.js" for native `fetch` proxy support and certificate trust

Abierto
  • ¿Algo no está bien?
#2,084 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@waldekmastykarz ya está trabajando en esto.

Desde el 5/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

documentation work in progress

Problem

The Node.js page states that native fetch "doesn't support configuring a proxy", and recommends NODE_TLS_REJECT_UNAUTHORIZED=0 for certificate errors. Both are outdated:

  • Node.js 24+ (and 22.21+) routes fetch and http(s) through HTTP(S)_PROXY when NODE_USE_ENV_PROXY=1 or --use-env-proxy is set.
  • NODE_EXTRA_CA_CERTS with the Dev Proxy root certificate is the safe alternative to disabling TLS verification. The certificate can be fetched with GET /proxy/rootCertificate?format=crt.

In all five evaluated runs, the agent worked this out from model knowledge rather than the docs. An agent that followed the page would disable TLS validation, or conclude that native fetch can't be proxied.

Proposal

  • Rewrite the "Native Node.js fetch API" section around NODE_USE_ENV_PROXY, including the version floor.
  • Replace NODE_TLS_REJECT_UNAUTHORIZED=0 with NODE_EXTRA_CA_CERTS, showing how to obtain the certificate through the API or CLI.
  • For older Node versions, keep the fallbacks: undici EnvHttpProxyAgent or global-agent.

Found while evaluating how coding agents use Dev Proxy: VS Code + GitHub Copilot Chat with Claude Sonnet 5.5, Dev Proxy 4.0.0 on Windows, 5 runs of the task "add a CI script that starts Dev Proxy in the background, starts and stops recording through the API around npm start, and shuts Dev Proxy down through the API".

Lenguaje dominante
C#
Estrellas
841
Forks
90
Merge medio
2 d 10 h
PR fusionados (30 d)
63

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotnet/dev-proxy

Todos los issues de dotnet/dev-proxy

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.