WebFetch fails when internet access is available only through a system proxy
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- desktop, networking
Línea de trabajo
Start by locating the WebFetch implementation and comparing its proxy handling with the GitHub Copilot CLI behavior described in the issue. Reproduce the failure with a system-configured proxy; done means WebFetch can retrieve external URLs through that proxy without the host-resolution error.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Short summary
In environments where outbound internet connectivity is provided via a system-configured proxy, the WebFetch tool fails to access external URLs and returns a host resolution error.
Affected version or release
v1.1.22
Installation context
No response
What happened?
When the GitHub Copilot agent attempts to retrieve content from a URL using the WebFetch tool, the request fails with the following error:
WebFetchBlockedUrlError: No such host is known. (os error 11001)
This occurs even when internet connectivity is available and functional through a properly configured system proxy.
Steps to reproduce
- Configure internet access through a system proxy.
- Start a GitHub Copilot agent session.
- Ask the agent to research a topic that requires fetching information from an external URL.
- Observe that the agent invokes the WebFetch tool and the request fails with:
WebFetchBlockedUrlError: No such host is known. (os error 11001)
Expected behavior
When a system proxy is configured, WebFetch should honor the operating system's proxy settings and route outbound requests through the proxy.
The behavior should be consistent with GitHub Copilot CLI, where web access works successfully in the same environment using the configured proxy.
Additional context
WebFetchBlockedUrlError: No such host is known. (os error 11001)
GitHub Copilot CLI can successfully perform web access in the same environment through the configured proxy.
The issue appears specific to the WebFetch implementation not honoring system proxy settings, all other features in Copilot app works.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 157
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/app
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de github/app
Issues similares
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
objective-see/LuLu#925 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
farion1231/cc-switch#7638 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
PolyMeilex/rfd#334 ·