- From: meacer <notifications@github.com>
- Date: Wed, 15 Nov 2023 00:32:01 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 15 November 2023 08:32:06 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>" Moved to network fetch. Now, steps 7.1, 7.3 and 7.5 of Network Fetch call HTTPS upgrade fallback in case of a network error. If I'm reading it correctly, streaming happens after step 12, so these steps aren't streaming related. Though, Step 7.5 seems to apply to POST requests which don't get upgraded, so it's not 100% clear to me that it should fallback. TLS client cert dialog indicates that the server is at least serving TLS with a valid config, so I don't think it makes sense to fallback there. The abort/cancelled case does not fallback. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1655#discussion_r1393831911 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1655/review/1731485866@github.com>
Received on Wednesday, 15 November 2023 08:32:06 UTC