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

@christhompson commented on this pull request.



> +<var>request</var> and <a for=/>response</a> <var>response</var>, run these steps:
+
+<ol>
+  <li><p>If <var>request</var>'s <code>https-upgrade</code> flag is not set, return
+  <var>response</var>.
+
+  <p class="note">This means <var>request</var> was not upgraded.
+
+  <li>
+    <p>Otherwise, the request was upgraded.
+
+    <p>If <var>response</var> is a network error, the upgrade failed. Initiate a fallback
+    load by running the following steps:
+
+     <ol>
+      <li><p>Create a synthetic redirect response <var>fallbackResponse</var> that redirects to

Done (in Chrome we also set a `Non-Authoritative-Reason: HttpsUpgrades` header, but I think we shouldn't spec that, same as we don't spec it for HSTS).

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

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