[VS Code] Spike: Classify and document HTTP connection issues
Problem
Users who use a less common networking setup (self-signed certificates, proxies) sometimes can't use the extension due to either poor documentation on how to configure the extension or due to the extension having bugs/missing features.
All the issues are captured in the parent epic: &12915
Output of this spike
- Based on open and closed certificate/Proxy issues (search issue tracker for certificate,SSL,proxy), ensure that:
-
Developer documentation contains a classification of the issues with an explanation of how to set up a development environment for them
-
Ensure that our user-facing docs https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/docs/user/ssl.md are up to date & that they are discoverable.
An example of discoverability might be a VS Code error notification that links to the docs. This notification would show every time a request fails due to certificate/proxy errors
-
- triage all the open SSL/Proxy issues, close duplicates
- In developer documentation, include resources so that people unfamiliar with self-signed certificates/proxy can get up to speed