- `Request` and `Response` objects from WHATWG Fetch - This means that `body` is `ReadableStream` from WHATWG Streams - The request object should be an extension of `Request` as `IncomingRequest`: - `req.connection` - `.protocolVersion` (`0.9`/`1`/`1.1`/`2`/`3`) - `.transport` (`tcp`/`unix`/`udp`) - `.remoteAddr` - On `unix`: `.path` - On `tcp`: `.family`, `.ip`, and `.port` - On `udp`: `.family`, `.ip`, and `.port` - `.localAddr` (same as `.remoteAddr`) - `.tls` - `.cipher` - `.peerCertificate` - `.version` - `.sni` - Possibly other data should be exposed. Needs investigation - what do existing runtimes expose? - Lifecycle of request / response data - How long can you read requests / response bodies - Can header access throw at some point - Related https://github.com/sindresorhus/ky/issues/797
RequestandResponseobjects from WHATWG FetchThis means that
bodyisReadableStreamfrom WHATWG StreamsThe request object should be an extension of
RequestasIncomingRequest:req.connection.protocolVersion(0.9/1/1.1/2/3).transport(tcp/unix/udp).remoteAddrunix:.pathtcp:.family,.ip, and.portudp:.family,.ip, and.port.localAddr(same as.remoteAddr).tls.cipher.peerCertificate.version.sniLifecycle of request / response data