How to install plugins behind a proxy with a self-signed certificate?

[ywmail]

I'm using vs code behind a proxy with a self-signed certificate, when i try to install plugins and typing "ext install ", it shows an error "unable to verify the first certificate".

[FloMaetschke]

same problem here.

[joaomoreno]

Duplicate of #69

[iamzhout]

suggest to reference atom's implementation, by using strict-ssl = false
https://atom.io/docs/v1.0.0/getting-started-installing-atom#setting-up-a-proxy

[joaomoreno]

This might not be a dupe after all, thanks @iamzhout!

[iamzhout]

@joaomoreno Welcome, hope this issue could be fixed soon :-) otherwise many corporate users may not be able to install extensions and make full use of vscode.

[RobertoMD]

Same issue here, but with a corporate proxy and authentication (no certificate). I get a getaddrinfo ENOTFOUND marketplace.visualstudio.com vmarketplace.visualstudio.com:443 (although I'm able to check & install upgrades with http_proxy and https_proxy env variables).

[timothymschier]

Same issue here, with the similar error to @RobertoMD:

getaddrinfo EAI_AGAIN marketplace.visualstudio.com:443

Have set http.proxy and https.proxy settings values. VS Code updates work fine; only Extensions Marketplace seems broken.

[ericherdzik-zz]

+1

[joaomoreno]

eaa5bcf introduces a new configuration setting http.proxyStrictSSL which when set to false will make the request bypass certificate chain validation