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

@christhompson commented on this pull request.



> +    following:
+
+    <ul>
+      <li><p>Set <var>request</var>'s URL to the value of <var>request</var>'s
+        <code>https-upgrade-fallback-url</code> flag</li>
+
+      <li><p>Set response to the result of running <a>HTTP-redirect fetch</a> given fetchParams and
+        <var>upgradedResponse</var>.</li>
+    </ul>
+  </li>
+
+  <li><p>Otherwise, the upgrade was successful. Return <var>upgradedResponse</var>.</li>
+</ol>
+
+<p>
+Optionally, user agents may implement a fast-fallback option by canceling slow fetches on upgraded

IMO this is already covered by implementations being able to timeout network requests in arbitrary ways, and this is mostly calling out that it can be useful for implementations to use a shorter timeout for these upgraded requests than they would normally (i.e., Chrome using a 3s timeout versus a complicated/OS-defined timeout process that is much longer). I think we could reword this as an aside or "note" to implementers?

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

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