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

Side by Side Diff: trunk/LayoutTests/http/tests/security/mixedContent/insecure-sync-post-xhr-allowed-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 ALERT: Executing script in the child window. 1 ALERT: Executing script in the child window.
2 ALERT: XHR POST opened. 2 ALERT: XHR POST opened.
3 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resour ces/frame-with-insecure-sync-xhr-post.html ran insecure content from http://loca lhost:8000/xmlhttprequest/resources/access-control-allow-lists.php?origin=*&head ers=Content-Type. 3 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resour ces/frame-with-insecure-sync-xhr-post.html displayed insecure content from http: //localhost:8000/xmlhttprequest/resources/access-control-allow-lists.php?origin= *&headers=Content-Type.
4 4
5 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resour ces/frame-with-insecure-sync-xhr-post.html ran insecure content from http://loca lhost:8000/xmlhttprequest/resources/access-control-allow-lists.php?origin=*&head ers=Content-Type. 5 CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resour ces/frame-with-insecure-sync-xhr-post.html displayed insecure content from http: //localhost:8000/xmlhttprequest/resources/access-control-allow-lists.php?origin= *&headers=Content-Type.
6 6
7 ALERT: XHR POST sent. 7 ALERT: XHR POST sent.
8 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. 8 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