Open Issues Need Help
View All on GitHubAn HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js
AI Summary: The GitHub issue addresses the absence of SSRF (Server-Side Request Forgery) protection in `undici` and Node.js's native `fetch` when making requests to arbitrary, user-controllable URLs. Unlike other HTTP libraries that support middleware or agents for filtering internal network access, `undici`/`fetch` currently lack a documented mechanism to prevent such attacks, posing a significant security vulnerability.
An HTTP/1.1 client, written from scratch for Node.js
AI Summary: The task is to enhance the `undici` Node.js HTTP client library by adding the handshake response details (status, statusText, headers) to the `undici:websocket:open` diagnostic event. This improvement aims to provide more comprehensive debugging information for WebSocket connections, aligning with the Chrome DevTools Protocol's `Network.webSocketHandshakeResponseReceived` event.
An HTTP/1.1 client, written from scratch for Node.js