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

@meacer commented on this pull request.



> +<p id=example-https-upgrade-good-https class=example><code>a.com</code> serves both
+<code>http://a.com</code> and <code>https://a.com</code>. An eligible request to
+<code>http://a.com</code> will be upgraded to <code>https://a.com</code>.
+
+<p id=example-https-upgrade-bad-https class=example><code>a.com</code> serves
+<code>http://a.com</code> but refuses connections on <code>https://a.com</code>. An eligible
+request to <code>http://a.com</code> will be upgraded to <code>https://a.com</code>, but the fetch
+will fail. A fallback request will be initiated to <code>http://a.com</code>.
+
+<p id=example-https-upgrade-allowlist class=example><code>site.test</code> serves
+<code>http://site.test</code> but refuses connections on <code>https://site.test</code>. Upon
+first request and fallback to <code>http://site.test</code>, the user agent stores the hostname
+in an allowlist with an expiration time of 7 days. In a future request, if <code>site.test</code>
+is still in this allowlist, the user agent will not upgrade <code>http://site.test</code> to
+<code>https://site.test</code>. The user agent will also set the new expiration time of the
+allowlist entry for <code>site.test</code> to 7 days from now.

Done in a few other places as well.

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

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