efrazer-oai f496b09bd1 Retry proxy CONNECT challenges with Windows authentication (#56000) ...

## Why

HTTPS requests and WebSocket connections on Windows need to authenticate when a proxy rejects `CONNECT` with status `407`.

## What changed

- Retry proxy challenges through the existing Windows authentication helper, using the signed-in user's Negotiate or NTLM credentials. Treat an origin `407` as a normal HTTP response.
- Bridge authenticated tunnels to the HTTP client through destination-specific named pipes, retaining redirect checks and TLS backend fallback without caching those tunnels across destinations.
- Carry explicit CA certificates and client identities into HTTPS proxy TLS configuration, and apply the configured connect timeout when opening authenticated HTTP tunnels.

GitOrigin-RevId: ec7d9168972a7a640350e5348cfca40307390fbf

2026-10-21 22:26:16 +00:00

..

src

Retry proxy CONNECT challenges with Windows authentication (#56000)

2026-10-21 22:26:16 +00:00

BUILD.bazel

websocket-client: add proxy-aware connector (#31622)

2026-07-08 12:57:27 -07:00

Cargo.toml

websocket-client: add proxy-aware connector (#31622)

2026-07-08 12:57:27 -07:00