Files
Carlos IL c890efab4f Bug 1838054 [wpt PR 40506] - Add WPTs for https upgrades and fallback, a=testonly
Automatic update from web-platform-tests
Add WPTs for https upgrades and fallback

The upgrades test currently fails in Chromium since HTTPS upgrades are
implemented at the //chrome level and tests run in content shell, but
it was still considered useful to have WPTs to document the spec proposal.
These are being added as "tentative" since the https upgrades spec
change has not landed yet.

Bug: 1394910
Change-Id: Ie94f3421abc7e14a676fa06d3c9d1fdf572ee096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4605846
Reviewed-by: Chris Thompson <[email protected]>
Commit-Queue: Carlos IL <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1156376}

--

wpt-commits: 7c5bebb89c041d4be30168a88e60deda08ed4bb2
wpt-pr: 40506
2023-06-21 14:34:37 +00:00

25 lines
794 B
HTML

<!DOCTYPE html>
<html>
<head>
<title>HTTPS Upgrades: Upgrade.</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/common/get-host-info.sub.js"></script>
</head>
<body>
<script>
setup({ single_test: true });
// HTTPS upgrades don't change custom ports, so this will load correctly if an HTTPS upgrade is performed,
// and will fail to load otherwise (since the port will be wrong for http).
var url = new URL("http://{{host}}:{{ports[https][0]}}/https-upgrades/resources/pass.html")
window.onmessage = function(event) {
if (event.data === "pass") {
done();
}
}
win = window.open(url)
</script>
</body>
</html>