[whatwg/fetch] Interop issue with range requests when the server sends more bytes than it says (#1295)

Source: https://news.ycombinator.com/item?id=28016543

Apparently if the server sends a content-length header of 1024 bytes, but the server instead sends a 4583-byte chunk, Firefox will fail the request and Chrome will continue.

Big providers like Netlify are doing this. Apparently they cannot figure out how to configure their server to send the correct (i.e. post-content-codings) content length: https://answers.netlify.com/t/add-unpacked-content-length-header-for-json-files/1804

(Maybe this should be a HTTPWG issue but I have more faith it'll get sorted out over here given how I've seen issues in that repo go...)

-- 
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/1295