Re: [fetch] Proposed backward-incompatible change: requiring cloning all requests/responses (#61)

Yeah, it's accidentally great misbehavior.

Regarding Response, Chrome 43 does allow calling `cache.put()` with a Response with null-body repeatedly. But it's less common to receive an empty response than a non-empty one. jakearchibald's guide at http://jakearchibald.com/2014/offline-cookbook/#on-network-response includes `response.clone()` call. Unless one is enthusiastic about optimization (omit calling .clone() for null body responses), the impact of the change would be small, I guess.

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