Re: [whatwg/fetch] HTTPS upgrades proposal (PR #1655)

@meacer commented on this pull request.



> @@ -6030,7 +6152,8 @@ optional boolean <var>forceNewConnection</var> (default false), run these steps:
       buffer of up to 64 kibibytes and store a part of <var>request</var>'s <a for=request>body</a>
       in that buffer. If the user agent reads from <var>request</var>'s <a for=request>body</a>
       beyond that buffer's size and the user agent needs to resend <var>request</var>, then instead
-      return a <a>network error</a>.
+      return the result of running <a>HTTPS upgrade fallback</a> given <var>request</var> and
+      <var>network error</var>.

Removed this and the change above, but this leaves only step 7.1 of network fetch where fallback navigations are handled. If that's the only place where navigation failures can result in a network error, that's OK, but wanted to double check.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1655#discussion_r1395356271
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1655/review/1733838358@github.com>