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

For context, Chrome seems to have explicit loop detection: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/chrome/browser/ssl/https_upgrades_interceptor.cc#519

The WPT is upgrading with `new URL("http://{{host}}:{{ports[https][0]}}/fetch/api/resources/redirect.py?location=" + …` which will trigger loop detection unless the query string is included.

What should happen on pages which redirect after a timeout like (www.bom.gov.au) which gets upgraded and then redirected to (http://www.bom.gov.au/akamai/https-redirect.html) which redirects using `window.location.replace` after 10 seconds. Using the 20 redirects limit would take over 3 minutes to get to the actual page.

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

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