Skip to content

Commit 7f8ab31

Browse files
committed
Add brief mention of browser storage options for JWTs
1 parent 10a0cd0 commit 7f8ab31

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

nodeJS/authentication/json_web_tokens.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ if (user?.password === req.body.password) {
5353
}
5454
```
5555
56-
<span id="sending-jwts">There are many ways JWTs can be sent to and from servers, such as in the response's "Authorization" header via the [Bearer scheme](https://security.stackexchange.com/questions/108662) or via httpOnly cookies. Since we have not yet covered how to handle cross-site cookies, the example above sends the JWT as a bearer token in the response's Authorization header.</span>
56+
<span id="sending-jwts">There are many ways JWTs can be sent to and from servers, such as in the response's "Authorization" header via the [Bearer scheme](https://security.stackexchange.com/questions/108662) or via httpOnly cookies. Since we have not yet covered how to handle cookies when the client and server are deployed on different domains, the example above sends the JWT as a bearer token in the response's Authorization header. When received, the client can store the JWT in a number of ways, such as in the same httpOnly cookie it came in, as well as extracting the token from the Authorization header then storing it in localStorage.</span>
5757
5858
<div class="lesson-note lesson-note--critical" markdown="1">
5959

0 commit comments

Comments
 (0)