Skip to content

fix(client-certificates): honor browser-level proxy and proxy.bypass - #42810

Closed
AbNoZ&v02 (Abnoz01) wants to merge 1 commit into
microsoft:mainfrom
Abnoz01:fix-42806
Closed

AbNoZ&v02 (Abnoz01) wants to merge 1 commit into
microsoft:mainfrom
Abnoz01:fix-42806

Conversation

@Abnoz01

Copy link
Copy Markdown
Contributor

Summary

  • With clientCertificates, all traffic goes through the local SOCKS interceptor, which must apply proxy settings itself. It only saw the context-level proxy, so a browser-level proxy was dropped and requests went direct.
  • createProxyAgent was called without a URL, so proxy.bypass was never evaluated and bypassed hosts were tunneled through the proxy.
  • Pass the browser-level proxy as a fallback and evaluate bypass per connection; add tests for both cases.

Fixes #42806

The client certificates interceptor replaces the browser proxy with a
local SOCKS proxy, so it has to apply the user's proxy settings itself.
It only received the context-level proxy and never evaluated bypass.

Fixes microsoft#42806
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.

[Bug]: clientCertificates ignores launch-level proxy and proxy.bypass, routing traffic outside the configured proxy

2 participants