Re: [whatwg/fetch] Handle failure while handling content codings (#710)

That there's also another, related issue here:  What if we support an encoding, but didn't advertise it?

Chrome used to let such requests through, applying decoding, but that led to interop issues with brotli (servers were sniffing the user agent instead of looking at the Accept-Encoding header, and sending Brotli responses over HTTP), so we changed, and now reject unadvertised encodings, at least if we recognize them.  That change led to issues with other servers that unconditionally send gzip - Chrome doesn't advertise gzip support when requesting media files, so it can use range requests.

-- 
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/pull/710#issuecomment-383614044