From 636094e6e0b28c840eda5433b9d41791673ceec8 Mon Sep 17 00:00:00 2001 From: Semona Igama Date: Fri, 25 Oct 2024 22:25:17 +0000 Subject: [PATCH] fixed small typo --- _source/_posts/2022-02-08-cookies-vs-tokens.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_source/_posts/2022-02-08-cookies-vs-tokens.adoc b/_source/_posts/2022-02-08-cookies-vs-tokens.adoc index b8daa37cab..7f43247823 100644 --- a/_source/_posts/2022-02-08-cookies-vs-tokens.adoc +++ b/_source/_posts/2022-02-08-cookies-vs-tokens.adoc @@ -102,7 +102,7 @@ Tokens—or JWTs in this context—are stateless in nature, meaning the server d * **Multiple storage options**: Tokens can be stored in a number of ways in browsers or front-end applications. -If you use a browser's local storage, tokens can't be accessed by a subdomain. However, they can be accessed and manipulated by any JavaScript code on the webpage, as well as by browser plugins. This isn't a recommended method: first, itposes a security risk, plus you must manage the storage. +If you use a browser's local storage, tokens can't be accessed by a subdomain. However, they can be accessed and manipulated by any JavaScript code on the webpage, as well as by browser plugins. This isn't a recommended method: first, it poses a security risk, plus you must manage the storage. Session storage is another way to store tokens. The drawback is that the token is destroyed when the browser is closed.