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
{{ message }}
Repository navigation
Add proxy support to http2 requests in the extension host #185098
This stopped working in VS Code 1.82 due to the Node 18 update that made fetch globally available, but apparently without support for system certificates.
When we checked the insiders build, it was working again, but since #194408 it only works with the "Http › Experimental: System Certificates V2" configuration activated.
Does this belong here or should I open a separate issue to track system certificate support for fetch?
Curious what the current state and plans for http2 proxy support are.
A lot of the discussion and blockers above are related to cert handling, which proxy-agent is also responsible for (although hopefully for not much longer: #247003 (comment)).
It's not clear whether any work was done on the proxy server handling side?
It turned out to be easier to add proxy support to fetch which supports http2 (though not enabled by default yet, see nodejs/undici#2750 (comment)). There is no work planned for adding support to the http2 module at the moment.
Activity
Load certificates in tls.connect (microsoft/vscode#185098)
Load certificates in tls.connect (microsoft/vscode#185098)
Load certificates in tls.connect (microsoft/vscode#185098)
Load certificates in tls.connect (microsoft/vscode#185098)
Load certificates in tls.connect (#185098)
Load certificates in net.connect (microsoft/vscode#185098)
Load certificates in net.connect (microsoft/vscode#185098)
Load certificates in net.connect (#185098)
Load certificates in net.connect (#185098)
13 remaining items
chrmarti commentedon Sep 25, 2023
Opened nodejs/node#49860 for Node.
Disable to investigate known issue (#185098)
Disable to investigate known issue (#185098)
kryops commentedon Oct 2, 2023
The system certificate loading V2 also seems to affect the native
fetchAPI.We conditionally include a polyfill to
node-fetch:This stopped working in VS Code 1.82 due to the Node 18 update that made
fetchglobally available, but apparently without support for system certificates.When we checked the insiders build, it was working again, but since #194408 it only works with the "Http › Experimental: System Certificates V2" configuration activated.
Does this belong here or should I open a separate issue to track system certificate support for
fetch?chrmarti commentedon Oct 2, 2023
Michael Manzinger (@kryops) This is the right place, thanks.
kryops commentedon Dec 12, 2024
The system certificate support for
fetchseems to have been fixed by #233104 🚀tmm1 commentedon Apr 29, 2025
Curious what the current state and plans for http2 proxy support are.
A lot of the discussion and blockers above are related to cert handling, which proxy-agent is also responsible for (although hopefully for not much longer: #247003 (comment)).
It's not clear whether any work was done on the proxy server handling side?
chrmarti commentedon May 5, 2025
It turned out to be easier to add proxy support to
fetchwhich supports http2 (though not enabled by default yet, see nodejs/undici#2750 (comment)). There is no work planned for adding support to thehttp2module at the moment.