Re: [fetch] Response content-length header almost always wrong (#67)

So `Content-Length` for responses is wrong due to https://fetch.spec.whatwg.org/#concept-http-network-fetch "handling content codings".

Currently `Content-Length` is not a forbidden header for responses, but it is for requests. That seems broken?

Fixing it for the Cache API but not for network responses seems wrong. I think fundamentally when you have an object the header should not be relevant anymore, but the original value might still be interesting for debugging purposes.

I wonder if @sleevi has any ideas.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/67#issuecomment-118636655