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

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

Issue 1018903002: Show deprecation warnings for header values in XHR according to RFC 7230 (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Created 5 years, 3 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
OLDNEW
1 CONSOLE WARNING: isValidHTTPHeaderValue() will be deprecated and will be removed in future.
1 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/xmlhttpreque st/access-control-response-with-body.html' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8000/xmlhttprequest/resour ces/access-control-allow-with-body.php'. This content should also be served over HTTPS. 2 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/xmlhttpreque st/access-control-response-with-body.html' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8000/xmlhttprequest/resour ces/access-control-allow-with-body.php'. This content should also be served over HTTPS.
2 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/xmlhttpreque st/access-control-response-with-body.html' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8000/xmlhttprequest/resour ces/access-control-allow-with-body.php'. This content should also be served over HTTPS. 3 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/xmlhttpreque st/access-control-response-with-body.html' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8000/xmlhttprequest/resour ces/access-control-allow-with-body.php'. This content should also be served over HTTPS.
3 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. 4 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