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

@christhompson commented on this pull request.



>  
+<div id=example-https-upgrade-slow-https class=example>
+ <p>
+  Optional fast-fallback example: <code>a.com</code> serves <code>http://a.com</code> and loads very
+  slowly over <code>https://a.com</code>.
+  An eligible request to <code>http://a.com</code> will be upgraded to <code>https://a.com</code>.
+  If the upgraded request doesn't return a response for N seconds, the fetch will be canceled.

I think it might be better to either explicitly make this implementation-defined, or to cut this entirely as it isn't particularly interesting for the spec IMO, as implementations can already trigger a network error for any number of reasons -- this is just a callout that Chrome specifically caps the network-level timeout to a shorter time than it normally does for this feature.

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

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