config http.proxy in workspace settings

[chesha1]

The http.proxy setting can only be configured in user settings. I’m wondering if it’s possible to set it in workspace settings instead.

When using a dev container, the http.proxy setting is passed to the container. However, the container cannot use the proxy on the local machine unless additional configuration is done.

If http.proxy could be configured directly in .vscode/settings.json or .devcontainer/devcontainer.json, it would make things much easier for users. Currently, we have to either modify the user settings each time or set up a more complex container network configuration.

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[chrmarti]

With a proxy running on localhost, how would you set http.proxy to fix it in the container? If you use the host's ip address in the Docker network, you still need to configure the proxy to also listen on that interface. Is there a simpler approach? (Looking for ways to make this work without the need for user configuration.)

[chesha1]

@chrmarti Thank you for your reply. I might have misunderstood your point. Are you saying that both the local machine and the dev container need to use the proxy, so setting http.proxy in the user settings won't help?

I think I didn't express myself clearly. Here's my situation: I have to run a proxy to overcome some network issues, but dev containers are sometimes hosted in environments where the network works fine without a proxy, such as in Codespaces. So if http.proxy could be set to an empty string through settings.json in the dev container, while retaining http://localhost:xxxx elsewhere, that would be great. The dev container and the local machine don't always need the same proxy.

[chrmarti]

We ignore the proxy setting from the local OS when connected via Remote-SSH. We should ignore the local http.proxy setting in that case too. As a workaround you could try to configure your proxy in the OS instead of the http.proxy setting.

It would make sense for http.proxy to be overridable in the machine settings. (Workspace settings might be the wrong scope, but maybe there are cases where having different proxies per workspace too.)

[davidolrik]

Having it in Workspace settings would be super useful.

[chrmarti]

You can now set https.proxy in the machine settings. Note that the http.useLocalProxyConfiguration machine setting controls whether or not the proxy config from the machine settings is applied (Remote-SSH and Remote Tunnels use the machine proxy settings by default, WSL and Dev Containers use the local proxy settings by default).

Resolved with microsoft/vscode-copilot-release#3821. This is available in VS Code 1.97.