- From: meacer <notifications@github.com>
- Date: Mon, 10 Jun 2024 17:34:09 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 June 2024 00:34:13 UTC
> @meacer Are you still working on this? Have Chrome's plans for this changed somehow? Apologies for my late reply. Chrome's plans for HTTPS Upgrades haven't changed. In fact HTTPS Upgrades are now enabled by default in Chrome, starting in Chrome 115. Therefore, this spec change is still a priority for us. Regarding redirect loop detection: I don't think it's possible to break out of loops between https upgrades and http fallbacks without any sort of detection logic. The https://www.bom.gov.au/ example above is a good one where this is needed. Given that most browsers will need this, I agree it makes sense to add it to the spec. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1655#issuecomment-2159552247 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1655/c2159552247@github.com>
Received on Tuesday, 11 June 2024 00:34:13 UTC