From a223336d3e2110845fb9f251171edf04ceabdafd Mon Sep 17 00:00:00 2001 From: LeviDing Date: Thu, 2 Apr 2020 20:34:57 +0800 Subject: [PATCH] Update article.md --- 2-ui/5-loading/03-onload-onerror/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2-ui/5-loading/03-onload-onerror/article.md b/2-ui/5-loading/03-onload-onerror/article.md index 3de42a06..162c9060 100644 --- a/2-ui/5-loading/03-onload-onerror/article.md +++ b/2-ui/5-loading/03-onload-onerror/article.md @@ -169,7 +169,7 @@ There are three levels of cross-origin access: 1. **No `crossorigin` attribute** -- access prohibited. 2. **`crossorigin="anonymous"`** -- access allowed if the server responds with the header `Access-Control-Allow-Origin` with `*` or our origin. Browser does not send authorization information and cookies to remote server. -3. **`crossorigin="use-credentials"`** -- access allowed if the server sends back the header `Access-Control-Allow-Origin` with our origin and `Access-Control-Allow-Credentials: true`. Browser sends authorization information and cookies to remote server. +3. **`crossorigin="use-credentials"`** -- access allowed if the server sends back the header `Access-Control-Allow-Origin` with our origin and `Access-Control-Allow-Credentials: true`. Browser sends authorization information and cookies to remote server. ```smart You can read more about cross-origin access in the chapter . It describes the `fetch` method for network requests, but the policy is exactly the same.