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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-sync-post-xhr-allowed-expected.txt

Issue 585873002: Show a warning when using sync xhr. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Added needsrebaseline for win_rel. Created 6 years, 1 month 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
OLDNEW
1 ALERT: Executing script in the child window. 1 ALERT: Executing script in the child window.
2 CONSOLE WARNING: Synchronous XMLHttpRequest on the main thread is deprecated bec ause of its detrimental effects to the end user's experience. For more help, che ck http://xhr.spec.whatwg.org/.
2 ALERT: XHR POST opened. 3 ALERT: XHR POST opened.
3 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-sync-xhr-post.html' was loaded over HTTP S, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8000/xmlh ttprequest/resources/access-control-allow-lists.php?origin=*&headers=Content-Typ e'. This content should also be served over HTTPS. 4 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-sync-xhr-post.html' was loaded over HTTP S, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8000/xmlh ttprequest/resources/access-control-allow-lists.php?origin=*&headers=Content-Typ e'. This content should also be served over HTTPS.
4 ALERT: XHR POST sent. 5 ALERT: XHR POST sent.
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. 6 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