<?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>JWT on Imran Khan</title>
    <link>https://imran-khan.com/tags/jwt/</link>
    <description>Recent content in JWT on Imran Khan</description>
    <generator>Hugo -- 0.127.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 08 Feb 2026 01:03:45 +0000</lastBuildDate>
    <atom:link href="https://imran-khan.com/tags/jwt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Where Does Your Login Live? JWT vs Sessions</title>
      <link>https://imran-khan.com/posts/what-is-the-core-different-between-jwt-and-session/</link>
      <pubDate>Sun, 08 Feb 2026 01:03:45 +0000</pubDate>
      <guid>https://imran-khan.com/posts/what-is-the-core-different-between-jwt-and-session/</guid>
      <description>JWT vs Sessions Ask which one to use and you&amp;rsquo;ll get two confident camps yelling past each other. Most of the disagreement comes from people comparing them without first being clear on what each one actually is, so let&amp;rsquo;s do that part properly and let the comparison fall out of it.
The problem both of them solve HTTP has no memory.
Each request arrives at the server as a total stranger.</description>
    </item>
  </channel>
</rss>
