Update article.md
This commit is contained in:
parent
2a6e87a6e9
commit
a223336d3e
1 changed files with 1 additions and 1 deletions
|
@ -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 <info:fetch-crossorigin>. It describes the `fetch` method for network requests, but the policy is exactly the same.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue