<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cookie on wid's blog</title><link>https://wid-blog.github.io/en/tags/cookie/</link><description>Recent content in Cookie on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 20 Mar 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/cookie/index.xml" rel="self" type="application/rss+xml"/><item><title>Session Authentication and JWT</title><link>https://wid-blog.github.io/en/posts/tech/security/session-and-jwt/</link><pubDate>Sat, 20 Mar 2021 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/security/session-and-jwt/</guid><description>HTTP is stateless. Maintaining user authentication requires storing state somewhere. This post covers the structure, trade-offs, and storage strategies of server-side sessions and client-side JWT tokens.</description></item></channel></rss>