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

Side by Side Diff: LayoutTests/http/tests/security/img-crossorigin-no-credentials-prompt-expected.txt

Issue 1300083002: Add suggestion to use "no-cors" with Fetch fails CORS check. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Patch CORS error expectation files to include message about Fetch CORS. Created 5 years, 4 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 ERROR: Image from origin 'http://localhost:8000' has been blocked from l oading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. The response had HTTP status code 401. 1 CONSOLE ERROR: Image from origin 'http://localhost:8000' has been blocked from l oading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. The response had HTTP status code 401. Alternative ly, if you want an opaque response, switch to The Fetch API in 'no-cors' mode.
2 CONSOLE ERROR: Image from origin 'http://localhost:8000' has been blocked from l oading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. The response had HTTP status code 401. 2 CONSOLE ERROR: Image from origin 'http://localhost:8000' has been blocked from l oading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. The response had HTTP status code 401. Alternative ly, if you want an opaque response, switch to The Fetch API in 'no-cors' mode.
3 No credentials should be prompted for on seeing a 401 for <img crossorigin>. 3 No credentials should be prompted for on seeing a 401 for <img crossorigin>.
4 4
5 PASS Non-CORS image resource failed to load 5 PASS Non-CORS image resource failed to load
6 PASS Non-CORS image resource failed to load 6 PASS Non-CORS image resource failed to load
7 TEST COMPLETE 7 TEST COMPLETE
8 8
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698