[whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1315)

Chrome is preparing to launch the feature from draft-ietf-dnsop-svcb-https-07 Section 8.5 that http:// requests get redirected to https:// on discovery of a matching HTTPS RR in DNS.  Firefox seems to have already recently lauched this feature (see https://www.mozilla.org/en-US/firefox/92.0/releasenotes/).

I think Fetch needs to be updated to acknowledge this behavior, similar to the references to HSTS.  Particularly, I think Section 4.9, point 9, (the text currently describing the HSTS redirection) needs a simple sentence or two of "or" explanation citing draft-ietf-dnsop-svcb-https and explaining when that causes the scheme to be changed to "https".

I can take a stab at a PR for this next week if there's general agreement that this is the right way to go to account for this new behavior.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1315