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

I already filed an issue for redirect behavior a while ago: https://github.com/whatwg/fetch/issues/1738

Only an [example](https://whatpr.org/fetch/1655.html#example-https-upgrade-redirect-loop) mentions it and it is fairly trivial:
`http://a.com` -> `https://a.com` -> `http://a.com`

There are plenty of common but more complicated cases like
`http://a.com` -> `https://a.com` -> `https://www.a.com` -> `http://www.a.com`

Chrome has implemented a quite thorough [redirect URL list](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ssl/https_upgrades_interceptor.h;l=136) to detect arbitrarily complicated loops.
Anne suggested that this should simply be covered by the 20 redirect limit.

Some redirect detection should be standardized. The fact that we have WPTs for it is a good indicator that we want to align on the same behavior here.

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

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