(invisible) HTTPS_PROXY settings overrule explicit HTTP_PROXY settings
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- csharp
- Área
- networking, tooling
Línea de trabajo
Start in ProxySettings.cs at private IWebProxy TryConfigureProxy(), especially the line checking _settings for the proxy setting name. Reproduce with https_proxy set without credentials alongside http_proxy and its credentials, then run libman restore. Done means explicit HTTP proxy credentials are honored and restore no longer produces the reported provider resolution errors.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Functional impact
If You configure only http_proxy + http_proxy.user + http_proxy.password, but the program gets a https_proxy URL from somewhere, Your settings will never be used and the restore function fails despite entering the right values.
I don't know how, but when debugging ProxySettings.cs, private IWebProxy TryConfigureProxy(), the line
if (_settings.TryGetValue(proxySettingName, out string proxyAddress)) (line 82)
returned a valid URL for https_proxy, even if it wasn't configured.
Therefore my own credentials were never used.
Minimal repro steps
-
configure:
https_proxy (with no credentials)
http_proxy
http_proxy.user
http_proxy.password -
Execute
libman restore -
You will get lots of errors, like
[LIB002]: The "jquery-easing@1.4.1" library could not be resolved by the "cdnjs" provider
Expected result
I would expect that the credentials I entered would make restore possible
I can understand that not every proxy needs user name + password
It would help, if at least in the documentation, the user would be instructed to set https_proxy + credentials first.
Unfortunately, the current documentation only mentions http_proxy settings.
- Lenguaje dominante
- C#
- Estrellas
- 486
- Forks
- 91
- 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 aspnet/LibraryManager
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
aspnet/LibraryManager#824 · 1 comentario · 3 reacciones ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
aspnet/LibraryManager#804 · 2 reacciones ·
-
Changelog for 3.0.114 Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 48/100
aspnet/LibraryManager#829 · 1 comentario · 3 reacciones ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
aspnet/LibraryManager#820 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
aspnet/LibraryManager#808 · 5 comentarios ·
Todos los issues de aspnet/LibraryManager
Issues similares
-
bug frontend good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
CS0162 "Unreachable code detected" warning from a MSBuildTemp .tmp file in every game project Abiertobug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
Type: enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
apache/arrow-adbc#4809 ·