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

Sorry. We just recalled that the current Chrome (stable 43) "incorrectly" behaves as @domenic's idea. Chrome had a bug that it errors the second `fetch()` in the following scenario:

```
var r = new Request('http://example.com');
fetch(r);
fetch(r);
```

In the Chromium bug entry @yutakahirano just posted, we've fixed it to conform to the current Fetch spec. So, till now, no one should be able to reuse a null-body Request for multiple `fetch()`es.

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