OLD | NEW |
| 1 CONSOLE WARNING: line 1: The page at 'https://127.0.0.1:8443/security/mixedConte
nt/resources/frame-with-redirect-http-to-https-script.html' was loaded over HTTP
S, but ran insecure content from 'http://127.0.0.1:8080/security/resources/redir
.php?url=https://127.0.0.1:8443/security/mixedContent/resources/script.js': this
content should also be loaded over HTTPS. |
| 2 |
1 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resou
rces/frame-with-redirect-http-to-https-script.html' was loaded over HTTPS, but r
an insecure content from 'http://127.0.0.1:8080/security/resources/redir.php?url
=https://127.0.0.1:8443/security/mixedContent/resources/script.js': this content
should also be loaded over HTTPS. | 3 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resou
rces/frame-with-redirect-http-to-https-script.html' was loaded over HTTPS, but r
an insecure content from 'http://127.0.0.1:8080/security/resources/redir.php?url
=https://127.0.0.1:8443/security/mixedContent/resources/script.js': this content
should also be loaded over HTTPS. |
2 | 4 |
3 This test loads a secure iframe that loads an insecure script (but with a tricky
redirect). We should trigger a mixed content callback because an active network
attacker could have redirected the script load to https://attacker.com. | 5 This test loads a secure iframe that loads an insecure script (but with a tricky
redirect). We should trigger a mixed content callback because an active network
attacker could have redirected the script load to https://attacker.com. |
4 | 6 |
5 | 7 |
OLD | NEW |