Re: [whatwg/fetch] Define how to handle bad content encoding (#657)

I'd prefer the majority behavior (response fulfills but body consumption fails). This specific WPT has the broken content-encoding right from the beginning, but in practice the broken content-encoding may not happen until we are already megabytes into the response. If we don't buffer that much there's no way it can be discovered at `fetch()` time.

-- 
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/657#issuecomment-355903624