yujonglee cfc651dcd5 fix(http): honor transport settings for Rust WebSockets (#47968) ... * fix(http): honor transport settings for Rust WebSockets The Responses WebSocket connected through tokio-tungstenite with its own native-roots TLS, so it ignored the configured CA bundle, verify flag, client certificate, proxies and timeouts. The handshake now goes through a pooled reqwest client (ClientVariant::WebSocket, HTTP/1.1, no redirects) and upgrades the response, so it shares the settings every other outbound request uses The upgrade response is checked for the Sec-WebSocket-Accept key, the Upgrade and Connection headers and a subprotocol that was offered Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(http): preserve native WebSocket trust and optional protocols * fix(http): allow plain WebSockets without native roots --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-10-28 07:32:41 -07:00
..
src	fix(http): honor transport settings for Rust WebSockets (#47968)	2026-10-28 07:32:41 -07:00
tests	fix(http): honor transport settings for Rust WebSockets (#47968)	2026-10-28 07:32:41 -07:00
AGENTS.md	refactor(rust): share anthropic types, request helpers, and streaming contracts across crates (#43426)	2026-09-27 14:53:12 -07:00
Cargo.toml	fix(http): honor transport settings for Rust WebSockets (#47968)	2026-10-28 07:32:41 -07:00