Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(245)

Side by Side Diff: trunk/LayoutTests/http/tests/security/mixedContent/insecure-xhr-in-main-frame-expected.txt

Issue 14793022: Revert 150055 "Consider "mixed content XHR" as mixed script inst..." (Closed) Base URL: svn://svn.chromium.org/blink/
Patch Set: Created 7 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/xmlhttprequest/access-contro l-response-with-body.html ran insecure content from http://localhost:8000/xmlhtt prequest/resources/access-control-allow-with-body.php. 1 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/xmlhttprequest/access-contro l-response-with-body.html displayed insecure content from http://localhost:8000/ xmlhttprequest/resources/access-control-allow-with-body.php.
2 2
3 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/xmlhttprequest/access-contro l-response-with-body.html ran insecure content from http://localhost:8000/xmlhtt prequest/resources/access-control-allow-with-body.php. 3 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/xmlhttprequest/access-contro l-response-with-body.html displayed insecure content from http://localhost:8000/ xmlhttprequest/resources/access-control-allow-with-body.php.
4 4
5 This test opens a HTTPS window that loads insecure data via XHR. We should trigg er a mixed content callback because the main frame in the window is HTTPS but no w has insecure data. 5 This test opens a HTTPS window that loads insecure data via XHR. We should trigg er a mixed content callback because the main frame in the window is HTTPS but no w has insecure data.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698