doc/editor_extensions/language_server/_index.md
The GitLab Language Server powers various GitLab editor extensions across IDEs.
The gitlab-lsp child process uses the proxy-from-env
NPM module to determine proxy settings from these environment variables:
NO_PROXYHTTPS_PROXYhttp_proxy (in lowercase)To configure the Language Server to use a proxy:
{{< tabs >}}
{{< tab title="Visual Studio Code" >}}
http.proxy
to point at your HTTP proxy.{{< /tab >}}
{{< tab title="JetBrains IDEs" >}}
{{< /tab >}}
{{< /tabs >}}
The Language Server is bundled with each editor extension for GitLab. To ensure you have the latest features and bug fixes available, update to the latest version of your extension:
You might encounter a 407 Access Denied (authentication_failed) error when using an authenticated proxy:
Request failed: Can't add GitLab account for https://gitlab.com. Check your instance URL and network connection.
Fetching resource from https://gitlab.com/api/v4/personal_access_tokens/self failed
To enable proxy authentication in the Language Server, follow the steps for your IDE:
{{< tabs >}}
{{< tab title="Visual Studio Code" >}}
http.proxy,
including username and password, to authenticate with your HTTP proxy.[!note] The VS Code extension does not support the legacy
http.proxyAuthorizationsetting in VS Code for authenticating the language server with an HTTP proxy. Support is proposed in issue 1672.
{{< /tab >}}
{{< tab title="JetBrains IDEs" >}}
{{< /tab >}}
{{< /tabs >}}
[!note] Bearer authentication is proposed in issue 548.