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

> It's subtle, but because only the scheme is changed the port remains unchanged. And when the scheme is "http" the port is either null or a non-80 integer (due to the URL parser). And when you go make a request and the scheme is "https" and the port is null, it uses 443. (This subtle behavior happens in multiple places though so I'm a bit hesitant to add notes all over, but maybe there's a way to make it work well.)

Should this behavior be changed and custom ports be exempt from upgrades? Configurations which use the same port for HTTP and HTTPS seem rare (I don't have any data). In some cases this does cause bugs like the one linked above: https://github.com/aio-libs/aiohttp/issues/8065


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

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