-
Notifications
You must be signed in to change notification settings - Fork 32.8k
Extensions proxy support #23164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have same problem now in #23166. Does your browser open https://marketplace.visualstudio.com/ with your settings? My VS Code tries to go there to get extensions and have got the proper list of them! But it cannot to install them. I try to open your https://vscode-update.azurewebsites.net/ in my browser and I see just |
I've spent the past day struggling with this. I was sure that my extensions search was working earlier, so I uninstalled the latest version and reinstalled working backwards. Turns out that I had to go back to the October release (1.7) before I could get the marketplace search working again. I'll probably stick here until it's fixed :( |
Proxy developments happening in #22214 |
I couldn't set up VSCode in a way that its Extensions tab works through my corporate proxy.
author.extension can be found in the URL when you open the extension in the browser Example: https://marketplace.visualstudio.com/items?itemName=PeterJausovec.vscode-docker |
Dear Team, Many thanks for this product used as a replacement of ISE on my every day work.
I work behind a corporate proxy that I manage to set up in vs code, it's working for Vs code update.
However I get 407 Authentication required when I try to install or check extension. I digg a lot on internet and find some workaround, most deprecated and non working.
Is there a way to make vs code use same proxy for extension and main program ?
Steps to Reproduce:
set up VS code proxy html : http://username:pass@proxy:port
Check for updates : Ok

Show popular extension : nothing appear and get the 407 in message analyser

Our corporate proxy use basic Auth, I try http.proxyStrictSSL either true or false and get same behavior
The text was updated successfully, but these errors were encountered: