jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Fix some typo

Browse source
This commit is contained in:
Rizky 2019-03-12 02:57:49 +00:00 • committed by GitHub
parent 364e707b2a
commit fdda11168c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
2-ui/5-data-storage/01-cookie/article.md
View file

@ -166,7 +166,7 @@ document.cookie = "user=John; max-age=0";
The cookie should be transferred only over HTTPS.
**By default if we set a cookie at `http://site.com`, then it also appears at `https://site.com` and vise versa.**
**By default, if we set a cookie at `http://site.com`, then it also appears at `https://site.com` and vise versa.**
That is, cookies only check the domain, they do not distinguish between the protocols.
@ -262,7 +262,7 @@ But if a cookie is `httpOnly`, then `document.cookie` doesn't see it, so it is p
## Appendix: Cookie functions
Here's a small set of functions to work with cookies, more conveinent than a manual modification of `document.cookie`.
Here's a small set of functions to work with cookies, more convenient than a manual modification of `document.cookie`.
There exist many cookie libraries for that, so these are for demo purposes. Fully working though:
@ -348,7 +348,7 @@ Together: [cookie.js](cookie.js).
A cookie is called "third-party" if it's placed by domain other than the user is visiting.
For instance:
1. A page at `site.com` loads an banner from another site: `<img src="https://ads.com/banner.png">`.
1. A page at `site.com` loads a banner from another site: `<img src="https://ads.com/banner.png">`.
2. Along with the banner, the remote server at `ads.com` may set `Set-Cookie` header with cookie like `id=1234`. Such cookie originates from `ads.com` domain, and will only be visible at `ads.com`:
![](cookie-third-party.png)
@ -357,7 +357,7 @@ For instance:
![](cookie-third-party-2.png)
4. What's even more important, when the users moves from `site.com` to another site `other.com` that also has a banners, then `ads.com` gets the cookie, as it belongs to `ads.com`, thus recognizing the visitor and tracking him as he moves between sites:
4. What's even more important, when the users moves from `site.com` to another site `other.com` that also has a banner, then `ads.com` gets the cookie, as it belongs to `ads.com`, thus recognizing the visitor and tracking him as he moves between sites:
![](cookie-third-party-3.png)