Index: LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked.html |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked.html b/LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked.html |
similarity index 94% |
copy from LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked.html |
copy to LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked.html |
index 26c9576b0cf2c175b35e3490d92c8ca3a9db2281..7b0a1a33bbf4ed120f14aa1ab7423c991f2b8bc0 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked.html |
+++ b/LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked.html |
@@ -20,7 +20,7 @@ trigger a mixed content callback even though the main frame in the window |
is HTTPS and is displaying insecure content, because we've set the preference |
to block this.</p> |
<script> |
-window.open("https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-image.html"); |
+window.open("https://127.0.0.1:8443/security/mixedContent/resources/frame-preloads-insecure-image.html"); |
</script> |
</body> |
</html> |