fetch raw bytes without decompressing (and sending accept-encoding)

This would solve…

Something that node-fetch have had is the possibility to avoid decompressing the body while also sending out accept-encoding. why would this be useful? if you make a request to abc.com on the behalf of a client (like in a proxy) and it respond with a content-length and a content-encoding then you wish to simply just send back all this response headers and pipe the data to back the client. but content-length will be a missmatch b/c the content-length will match the compressed size and what you are actually piping back to the client will be the uncompressed size

The implementation should look like…

I have also considered…

Additional context

node-fetch has compress: true but if i could rename it, then it would be decompressResponseBody: boolean and default that to true

[mcollina]

@vlovich @jasnell my understanding is that you are asking for undici fetch to support cache-control: no-transform to avoid automatically decompressing the body. This behavior is currently present in browsers. If my assessment is correct, then could you send a PR implementing this?

This issue was about adding a custom, non-spec option for doing the same client side. I’d prefer we do not add any non-spec compliant option without passing through WinterCG.

[mcollina]

Then I think it’s out of scope. Maybe open an issue in WinterCG to see if there is appetite for standardizing this feature.