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

@mnot commented on this pull request.



> @@ -4593,6 +4593,31 @@ Range Requests</cite>. [[HTTP-RANGE]] However, this is not widely supported by b
    using <var>request</var>.
   </ol>
 
+ <li>
+  <p>If <var>response</var>'s <a for=response>status</a> is 421, then:
+
+  <ol>
+   <li>
+    <p>If the ongoing fetch is <a for=fetch>terminated</a>, then:
+
+    <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>.

OK. I was assuming that the common case here would be that the fetch aborts for some reason, and the initiating code wants to automatically re-fetch based upon request details that it has buffered. I suppose it can do so based upon the network error, but 421 conveys a little bit of additional information -- that the request definitely hasn't changed any server-side state.

-- 
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_r568338558