Khafra

@ronag undici sets `connection: close` by default, but we should also support keepalive imo? Or document it.

`global` in this case could mean a worker, which would be applicable to node (although there are other issues with fetch in worker threads). You're right about it not involving...

but in that case it's not something we can fix, so this is just a documentation issue

> Is disabling of this connection: keep-alive HTTP header something that can be set in RequestInit No, neither undici or the fetch spec allow modifying the connection header. If you...

benchmarks: ```js import { Response as UndiciResponse } from './index.js' import { cronometro } from 'cronometro' await cronometro({ async 'undici Response' () { await new UndiciResponse('abc').text() }, async 'global Response'...

I understand, but 10% performance improvement is significant for the small change I made. We still extract the body (convert it to a readable web stream), but instead of reading...

I think it's important to note the following with this change: 1. no part of the spec is removed or modified: body's source is part of the fetch spec; a...

I know you're not blocking the change but I typically don't like adding or changing things that are disapproved.

cc @ronag

Can - yes (?), as your PR did that. Should - yes, we can always revert the change once it's fixed upstream. We've implemented plenty of workarounds for bugs in...