chromium/src
0
Fork 0
Code Activity

Fix only-top-level-navigation-hsts-upgrade test's comment

Browse Source 
The comment referred to the old domain name and file name, this CL
updates them.

Bug: 40725781
Change-Id: I19df6deff1abccf64e631a35f3f23eeda6e90d6d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347822
Auto-Submit: Steven Bingler <bingler@chromium.org>
Reviewed-by: Kyra Seevers <kyraseevers@chromium.org>
Commit-Queue: Steven Bingler <bingler@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431521}
This commit is contained in:
sbingler
2025-03-12 08:27:30 -07:00
committed by Chromium LUCI CQ
parent f50c95ca3a
commit 9479ba47fb
1 changed files with 3 additions and 3 deletions

6
third_party/blink/web_tests/external/wpt/hsts/only-top-level-navigation-hsts-upgrade.tentative.sub.html vendored

@ -10,10 +10,10 @@
// then mixed content blocking will prevent HSTS from working.
// 0) Confirm that insecure iframes can be loaded.
// 1) Pin hsts-example.test to the HSTS via hsts.php
// 1) Pin the alt hostname to the HSTS via hsts.html
// 2) Attempt to load an iframe via http. This should fail because
// http://hsts-example.test:8442 is an invalid origin *and* HSTS should not
// upgrade the iframe navigation to https.
// http://{{hosts[alt][]}}:{{ports[https][0]}} is an invalid origin *and*
// HSTS should not upgrade the iframe navigation to https.
// 3) Open a new window and navigate it to the same http origin. This should
// successfully be upgraded to https, load, and then postMessage its origin.