- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 21 Oct 2022 09:29:06 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 21 October 2022 16:29:18 UTC
@annevk commented on this pull request. > @@ -4400,12 +4406,17 @@ steps: <p class=note>This covers the case of <var>response</var> being a <a>network error</a>. + <li><p>Let <var>responseStatus</var> be 0 if <var>fetchParams</var>'s + <a for="fetch params">request</a>'s <a for=request>mode</a> is "<code>navigate</code>" and + <var>response</var>'s <a for=response>has-cross-origin-redirects</a> is true; otherwise + <var>response</var>'s <a for=response>status</a>. I was about to merge this, but I don't understand how this protects the response status when mode isn't "navigate". Shouldn't we be using the timing allow passed flag in that case? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1468#pullrequestreview-1151242666 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1468/review/1151242666@github.com>
Received on Friday, 21 October 2022 16:29:18 UTC