- From: Will Hawkins <notifications@github.com>
- Date: Mon, 19 Dec 2022 10:13:56 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/1577@github.com>
https://fetch.spec.whatwg.org/commit-snapshots/84ea7dbb5793fd7e560bb80ea53c31cf32bb513f/#connections > To obtain a connection, given a network partition key key, URL url, boolean credentials, an optional new connection setting new \(default "no"\), and an optional boolean http3Only > \(default false\), run these steps: I am sorry to have to ask this question, but I was looking through the spec to help me understand how fetch could help me with a very special use case. In particular, we would really like the application to use new connections for particular requests. Needless to say, when I saw the *new connection setting* flag in the *obtain a connection* operation, I was definitely excited. However, as I follow it through the spec, it does not appear that there are any places that supply the *new connection setting* to the *obtain a connection* operation. From what I can tell, *obtain a connection* is used in *HTTP-network fetch* which is (only) used by *HTTP-network-or-cache fetch* which is used in several places. It does not appear, though, that any of those places specify the new connection flag as an argument. I am *sure* that I am missing something, but I cannot seem to figure out what it is. If you could help, I would greatly appreciate it! Thank you! Will -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1577 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1577@github.com>
Received on Monday, 19 December 2022 18:14:08 UTC