README (1103B)
1 This directory tests conformance to HTTPS Upgrading feature of Fetch spec. 2 HTTPS Upgrading automatically upgrades main frame HTTP navigations to HTTPS and 3 falls back to the original HTTP URL if the upgraded HTTPS URL isn't available. 4 5 In practice, HTTPS Upgrading won't work properly with URLs with non-default 6 ports. This is because the upgrade logic can't guess the HTTPS port and has to 7 use the same non-default port number for the upgraded HTTPS URL as the HTTP URL. 8 In other words, upgrading http://example.com:8123 to https://example.com:8123 9 won't work because the server can't serve both http and https on the same port. 10 11 The tests in this directory rely on this fact: 12 - If HTTPS Upgrading is enabled, http://{{host}}:{{https-port}} will be upgraded 13 to https://{{host}}:{{https-port}} and load properly. 14 - Otherwise, http://{{host}}:{{https-port}} will remain unchanged and won't 15 load, since the server serves http URLs on {{http-port}} instead. 16 17 Therefore, the simplest way to run these tests is through 18 [wpt.live](http://wpt.live/https-upgrades) which serves the files over default 19 ports.