Re: [whatwg/fetch] Content codings (Content-Encoding) (#716)

Changes to "handling content codings":

1. Iterate over codings and do decoding for each if them, if supported, and retain input as-is otherwise. If decoding fails, return failure.
2. Pass in the response or some such so you can determine the HTTPS bit. (Might as well move parsing of `Content-Encoding` there.)

Questions:

1. Should we define a limit? Maybe at least a lower bound.
2. Can we make unsupported values an error? Probably not...
3. ...

-- 
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/716#issuecomment-383562558