Skip to content

Conversation

@EhabY
Copy link
Collaborator

@EhabY EhabY commented Jan 26, 2026

Add support for VS Code's proxy settings that were not previously respected:

  • http.noProxy: Falls back when coder.proxyBypass is not set
  • http.proxyAuthorization: Passed directly as Proxy-Authorization header
  • http.proxyStrictSSL: Combined with coder.insecure for TLS verification

Also fixes a bug in proxy.ts where the scheme condition was inverted, causing schemes to be added when they already existed.

Fixes #755

@EhabY EhabY self-assigned this Jan 26, 2026
@EhabY EhabY force-pushed the support-vs-code-proxy-settings branch 2 times, most recently from 2c996d8 to 11d7ce4 Compare January 26, 2026 21:24
Copy link
Member

@mafredri mafredri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor concern, but otherwise LGTM.

EhabY added 2 commits January 27, 2026 12:21
Add support for VS Code's proxy settings that were not previously respected:
- http.noProxy: Falls back when coder.proxyBypass is not set
- http.proxyAuthorization: Passed directly as Proxy-Authorization header
- http.proxyStrictSSL: Combined with coder.insecure for TLS verification

Also fixes a bug in proxy.ts where the scheme condition was inverted,
causing schemes to be added when they already existed.
@EhabY EhabY force-pushed the support-vs-code-proxy-settings branch from 11d7ce4 to b81501b Compare January 27, 2026 09:22
@EhabY EhabY merged commit 1133a0f into coder:main Jan 27, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Respect VS Code's built-in proxy settings

3 participants