Support users behind firewall/proxy

[radeksimko]

Problem Statement

Some of our end users work from behind a more restrictive firewall usually set up by their company. The extension will install or update LS automatically upon activation and/or every 24 hours. Not having access to releases.hashicorp.com from which LS releases are downloaded leads to a very poor UX at this moment:

User Impact

Any user which is behind a restrictive firewall is impacted.

Expected User Experience

VS Code Proxy Settings

VS Code has its own config option for proxy, as mentioned in #665 (comment)

The extension would ideally read it and used it for any outgoing requests while discovering and downloading LS.

Proxy Settings From Environment

It is very common for users to put proxy settings into the conventional http_proxy and https_proxy environment variables.

Similar to above the extension would ideally read it and used it for any outgoing requests while discovering and downloading LS.

Blocked Requests Surfaced

A more helpful error is surfaced instead of the vague one above.

Proposal

• explore how to get static proxy settings from VS Code
• pass that proxy settings to js-releases
• confirm that js-releases reads proxy settings from conventional environment variables and that VS Code would pass these environment variables down to the extension process automatically when passed to VS Code
• catch errors which are likely caused by a restrictive proxy (e.g. Proxy Authentication Required or unable to get local issuer certificate) and surface them either directly, or in a more human-readable format

[radeksimko]

Since 2.20.0 (released 1st March 2022) we no longer install language server at runtime, it is instead embedded into the vsix. Therefore firewall and other network related issues with installation should no longer exist as there's no installation at runtime.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.