[whatwg/fetch] Partition HTTP Connections (#1063)

Extend the HTTP cache partitioning logic to partition connections as well. This doesn't cover everything that will need to be partitioned, since much of it isn't even capturing in the fetch spec yet (browser-managed DNS caches, WebSocket connections over H2/H3 proxies, H2/H3 sessions, TLS/H3 session resumption cache, cache of metadata about H3-capable servers, HTTP auth cache, etc).

This addresses parts of issue #917.

- [ ] At least two implementers are interested (and none opposed):
   * Chrome
   * FireFox
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * ...
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/master/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: https://crbug.com/963480

   * Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1572544

   * Safari: …

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/1063


-- Commit Summary --

  * .
  * Clarify things around secondKey
  * .

-- File Changes --

    M fetch.bs (33)

-- Patch Links --

https://github.com/whatwg/fetch/pull/1063.patch

https://github.com/whatwg/fetch/pull/1063.diff


-- 
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/1063