Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653)

There is nothing stopping a user of fetch() from creating a GzipStream as Ben suggests and adding the Content-Encoding header field.  And I think that is a fine outcome.  Note that this depends on a number of things: knowing that the server supports it (see [RFC 7694](http://httpwg.org/specs/rfc7694.html)), and knowing that you aren't mixing attacker-controlled and confidential information in a way that might leak to leaks.

It might not even be prohibitively expensive performance-wise to run gzip or brotli and friends in JS.  Having a native implementation is certainly possible.  This is something of a niche use case, but there are probably other use cases that might benefit from a general compression mechanism.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/653#issuecomment-355860252