- From: Jake Archibald <notifications@github.com>
- Date: Wed, 24 Jun 2015 08:39:06 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Wednesday, 24 June 2015 15:39:38 UTC
Is there a summary of the issues caused by the current model? Or is it just confusion over which apis read response bodies? If `getReader()` sets the flag, `fetch` would effectively call `getReader()` to get the response body. `put(request, response)` could call `getReader()` of the response, but not the request as bodies are ignored. `cache.match(request)` wouldn't set the flag because body is not needed in the matching process - still trying to get my head around why this is so bad. Assuming there's huge benefit to making this change, I want it to be possible to ship it in a way that doesn't insta-break existing sites. I guess this means allowing `.put(req, res)` to work even if `req` is used, flagging that in the console, and maybe even recording this so we can reach out to high traffic sites ahead of going strict with `.put`. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/61#issuecomment-114914738
Received on Wednesday, 24 June 2015 15:39:38 UTC