Runtime's fetch client, might not support the encodings that the browser client supports.
The relevant issue was because Undici (Node.js) fetch does not support zstd but in general, it is an unsafe thing to pass through.
For performance, users can explicitly enable a supported accept-encoding to the server or we might later identify what runtime supports and set that instead (instead of the proxy incoming request)
Ref: https://github.com/nitrojs/nitro/issues/2880
Runtime's fetch client, might not support the encodings that the browser client supports.
The relevant issue was because Undici (Node.js) fetch does not support
zstdbut in general, it is an unsafe thing to pass through.For performance, users can explicitly enable a supported
accept-encodingto the server or we might later identify what runtime supports and set that instead (instead of the proxy incoming request)