-
Notifications
You must be signed in to change notification settings - Fork 448
Can we get this to work through a proxy? #19
Comments
Hi ozippy. Unfortunately, it appears that the vso-node-api package that the VS Code extension uses still needs true proxy support. See microsoft/azure-devops-node-api#35. Although there is an active PR out for adding the support, so hopefully that will come soon. |
Hi @ozippy. So the change for this went in a while back (Oct 2016). You'd need to set the HTTP_PROXY or HTTPS_PROXY variable to your proxy server and include the port. I'd be very interested in knowing if this works out for you. |
Hi @jeffyoung . I'm behind a corporate proxy that requires auth. Can't make vscode connect through it no matter the value of the HTTP(S)_PROXY env vars or the http.proxy setting in vscode itself. Even if I set a name & pass in the proxy value. Is this still an outstanding item? I have a colleague who's really keen to be using vscode for all his front-end dev, but half our projects are TFVC and half Git. |
Debug logging in case it's useful: 2017-05-10T14:27:31.477Z - debug: [09604] Reinitializing due to onDidChangeConfiguration |
Hi @RobPurcellCgl, thanks for trying out the extension. It looks like this (authenticated proxies) is still an issue in the vso-node-api library (which is used by the VS Code extension). The extension currently uses version ^5.1.1 but it appears there's been a major update to it (pushing it past v6) that made some bigger changes. Looking in the code there, it appears it's still a TODO. |
At this point, an unauthenticated proxy should work (by setting http_proxy and https_proxy env vars; http_proxy in VS Code settings will not do). Authenticated proxies are still not supported by the vsts-node-api dependency. |
OK, thanks Jeff. We've made a couple of simple TF CLI scripts for him to check in/out for now. Bit of a faff though. We'll wait on this getting sorted. |
This looks really good. I have VSCode working through our proxy and have been able to install the extension. When I open a repo from VSTS, I think it connects using my token, but then it shows an ECONNREFUSED error when I hover over the Team icon in the status bar.
Thanks
The text was updated successfully, but these errors were encountered: