- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 23 Oct 2019 01:24:24 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 23 October 2019 08:24:27 UTC
I think that's mostly covered already as https://fetch.spec.whatwg.org/#concept-http-network-fetch is pretty explicit when we finally get to making a request: "Set response to the result of making an HTTP request over connection using request with the following caveats". I suppose we could further clarify there though that the HTTP cache is not involved and only consulted during https://fetch.spec.whatwg.org/#concept-http-network-or-cache-fetch. But we could do that independently from this change I think. To restate my comment above, I think the PR as-is is okay; the problem is with existing implementations in browsers, inadequate test coverage for the change, and lack of clarity whether implementations are prepared to align on this. (Reading #722 again it sounds like both Chrome and Firefox would have difficulty adopting this change and are not necessarily prepared to go through the trouble.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/788#issuecomment-545329337
Received on Wednesday, 23 October 2019 08:24:27 UTC