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

Hello,

I made a few changes to this PR:
1. Added an example for custom ports
2. Added an example for redirect loops
3. Moved the upgrade step after HSTS upgrades to avoid setting a fallback URL when an HSTS upgrade is done

(3) also makes the flow more in-line with the HTTPS Upgrades implementation in Chrome. Chrome does HTTPS upgrading before HSTS, but first checks if the URL would be upgraded by HSTS. If yes, it doesn't continue with the upgrade and lets HSTS handle the navigation.

This latest change should handle all of the concerns raised in the comment thread before. Please let me know if the latest diff looks good, thanks.

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

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