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

The tentative resolution here is that browser implementations should only use `Content-Length` in the network layer. After that it is no longer relevant, but we'll keep it around in the `Response` object. It's just no longer accurate necessarily. This is more or less how the specifications will end up being layered anyway, but I might add a note in Fetch.

Any objections?

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