## Summary - add managed proxy env wiring for websocket-specific variables (`WS_PROXY`/`WSS_PROXY`, including lowercase) - keep websocket proxy vars aligned with the existing managed HTTP proxy endpoint - add CONNECT regression tests to cover allowlist and denylist decisions (websocket tunnel path) - document websocket proxy usage and CONNECT policy behavior in the network proxy README ## Testing - just fmt - cargo test -p codex-network-proxy - cargo clippy -p codex-network-proxy Co-authored-by: Codex <199175422+chatgpt-codex-connector[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| admin.rs | ||
| config.rs | ||
| http_proxy.rs | ||
| lib.rs | ||
| metadata.rs | ||
| network_policy.rs | ||
| policy.rs | ||
| proxy.rs | ||
| reasons.rs | ||
| responses.rs | ||
| runtime.rs | ||
| socks5.rs | ||
| state.rs | ||
| upstream.rs | ||