- From: meacer <notifications@github.com>
- Date: Mon, 13 Nov 2023 00:32:41 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 13 November 2023 08:32:49 UTC
@meacer commented on this pull request. > @@ -5157,8 +5279,6 @@ these steps: <p>If one of the following is true <ul class=brief> - <li><p><var>response</var>'s <a for=response>type</a> is "<code>error</code>" As we discussed in chat, I'll move this to HTTP network fetch. There are several `return a network error` steps in HTTP Network fetch. I think HTTPS upgrading fallback algorithm should run for all of those network errors. So I'm planning to replace `return a network error` steps with `return <a>HTTPS upgrade fallback</a> given <var>request</var> and <var>network error</var>` in HTTP Network Fetch (including one step where an `appropriate network error` is returned instead of simply `network error`). Does that sound about right? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1655#discussion_r1390756226 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1655/review/1726758622@github.com>
Received on Monday, 13 November 2023 08:32:49 UTC