Re: [whatwg/fetch] Add HTTP fetch step on 421. (#1141)

@annevk commented on this pull request.



> +    <ol>
+     <li><p>Let <var>aborted</var> be the termination's aborted flag.
+
+     <li><p>If <var>aborted</var> is set, then return an <a>aborted network error</a>.
+
+     <li><p>Return a <a>network error</a>.
+    </ol>
+
+   <li>
+    <p>If <var>actualResponse</var>'s <a for=response>status</a> is 421,
+     <var>request</var>'s <a for=request>body</a> is non-null, and
+     <var>request</var>'s <a for=request>body</a>'s <a for=body>source</a> is
+      null, then return a <a>network error</a>.
+
+   <li><p>Set <var>response</var> to the result of performing an <a>HTTP-network-or-cache fetch</a>
+   using <var>request</var>.

I'm not talking about the HTTP cache, I'm talking about the connection pool "cache". This needs to ensure you get a new connection if I understand it correctly, not reuse an existing one. (It's probably fine to invoke HTTP-network fetch directly, but you'd still need to signal that it needs a fresh connection, perhaps with a new argument in a few places.)

-- 
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/1141#discussion_r569166931