You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start VS Code and set "http.proxySupport": "off" in settings.json
Make an HTTP Request (in my case I tested authorization with azurecore provider (similar to microsoft authenticator provider) - from Azure Data Studio)
Notice HTTP request will fail.
Expected: Since http.proxysupport is OFF, authentication should not use proxy URL.
Explanation
VSCode should not send Proxy URL in request if proxy support is disabled. As there is no other way to override these settings and skip any injected HTTP_PROXY env variables if users don't want to use Proxy. The Proxy agent set in code despite this proxy support turned "off" causes authentication failures when proxy is not expected to play a role.
I was able to make it work in ADS by updating code to what I mentioned above.
Also, yes, I'm testing ADS, but since codebase in src/vs/platform that's why I brought it up since this issue applies to VSCode core design.
Steps to Reproduce:
Expected: Since http.proxysupport is OFF, authentication should not use proxy URL.
Explanation
VSCode should not send Proxy URL in request if proxy support is disabled. As there is no other way to override these settings and skip any injected HTTP_PROXY env variables if users don't want to use Proxy. The Proxy agent set in code despite this proxy support turned "off" causes authentication failures when proxy is not expected to play a role.
I have also tried to use startup params from here, but they don't work either: https://code.visualstudio.com/docs/setup/network#_proxy-server-support
Code Issue
I believe this code is responsible to set Proxy Agent:
vscode/src/vs/platform/request/node/requestService.ts
Lines 83 to 93 in 3df5eee
I think all these 3 settings (agent, strictSSL, proxy headers) should be set only when proxy support is enabled.
The text was updated successfully, but these errors were encountered: