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

@annevk @shivanigithub @domenic @mnot thoughts? Not sure if this is the best approach.

In terms of testing, it looks like BasicHttpServer doesn't exposed any sort of connection ID, but it does expose port. So it seems like the best we could do without touching BasicHttpServer itself is to make a request handler that exposes the client-side port each request is using, and make sure the same ports are used to service requests made by two top-level browsing contexts using different origins.  Haven't looked into the exact mechanics of how to share observed port data, but could just use link decoration with a list of previously observed ports, if there's nothing more elegant available.

-- 
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#issuecomment-665136263