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

@annevk commented on this pull request.



> +
+     <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> on a new <a>connection</a>, which
+      is <a lt="obtain a connection">obtained</a> using true
+      <var>bypassConnectionPool</var>.
+      User agents should have an <a>implementation-defined</a> recursion limit.

Similar to the above this needs to be a new argument to HTTP-network-or-cache fetch instead, right? So that it does the right thing when a connection is established.

>  
 <ol>
- <li><p>If the user agent's <a>connection pool</a> contains a <a>connection</a> whose <b>key</b> is
+ <li><p>If <var>bypassConnectionPool</var> is false, the user agent's <a>connection pool</a> contains a <a>connection</a> whose <b>key</b> is

is false and the user agent's*

-- 
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#pullrequestreview-586271860