You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: auto-detect HTTP proxy tunneling
Signed-off-by: Matteo Collina <hello@matteocollina.com>
* test: enable proxy tunneling in bundle test
Signed-off-by: Matteo Collina <hello@matteocollina.com>
* fix: forward over HTTPS proxy per RFC 9112 §3.2.2
Tunnel decision now depends on the request protocol only. HTTP requests
through an HTTPS proxy use absolute-form request-target over TLS to the
proxy instead of CONNECT, matching Node's built-in http.request and
RFC 9112. HTTPS requests still tunnel via CONNECT.
Http1ProxyWrapper pins the proxy SNI so the inner Client does not derive
it from the rewritten Host header, and wraps ERR_TLS_CERT_ALTNAME_INVALID
into SecureProxyConnectionError for parity with the tunneling path.
Signed-off-by: Matteo Collina <hello@matteocollina.com>
* ci: disable shared-builtin job pending nodejs/node sync
The forwarding fix from #5116 is in undici main but the embedded undici
in nodejs/node still expects the old semantics, so the shared-builtin
build fails until Node.js 26 ships a release embedding the updated
undici. Comment is left in place to re-enable for Node.js 26 at that
point. Node.js 24 stays off as the change is not being backported.
Signed-off-by: Matteo Collina <hello@matteocollina.com>
* fix: force HTTP/1.1 for proxy forwarding
* test: force tunneling for CONNECT regression
---------
Signed-off-by: Matteo Collina <hello@matteocollina.com>
0 commit comments