Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I created a new project and launched an Ubuntu development container.

Without any special settings, the proxy of the started environment was set in /etc/environment as follows.

vscode ➜ /workspaces/etcenv $ cat /etc/environment 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
HTTPS_PROXY="http://proxy.xxx.co.jp:8080"
https_proxy="http://proxy.xxx.co.jp:8080"
NO_PROXY="localhost,127.0.0.1,169.254.169.254,169.254.170.2,xxx.co.jp"
no_proxy="localhost,127.0.0.1,169.254.169.254,169.254.170.2,xxx.co.jp"
HTTP_PROXY="http://proxy.xxx.co.jp:8080"
http_proxy="http://proxy.xxx.co.jp:8080"
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
I've noticed that the addition of capitalized Proxy settings has broken some existing projects.
Earlier versions of VSCode probably didn't do this.
Is this guess correct? Is it possible to disable the setting?
The version I'm using now is:
Version: 1.73.1 (system setup)
Commit: 6261075646f055b99068d3688932416f2346dd3b
Date: 2022-11-09T04:27:29.066Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
ms-vscode-remote.remote-ssh v0.92.0
An existing project was working in VSCode a couple of months ago.
I don't know if the proxy was set in /etc/environment of the existing project, but I was doing the same operation many times every day with the devcontainer, so I guess the proxy was not set.
I expected the latest version of VSCode to behave the same.
but, Existing projects, which have not changed, are now not working as they used to due to the capitalized proxy set in /etc/environment.
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.