<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SameSite on Nalar</title>
    <link>https://nalar.dev/tags/samesite/</link>
    <description>Recent content in SameSite on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/samesite/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SameSite Cookies Draw a Site Boundary That Is Broader Than Origin</title>
      <link>https://nalar.dev/samesite-cookies-draw-a-site-boundary-that-is-broader-than-origin/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/samesite-cookies-draw-a-site-boundary-that-is-broader-than-origin/</guid>
      <description>&lt;h1 id=&#34;samesite-cookies-draw-a-site-boundary-that-is-broader-than-origin&#34;&gt;SameSite Cookies Draw a Site Boundary That Is Broader Than Origin&lt;/h1&gt;&#xA;&lt;p&gt;Two HTTPS applications can be isolated by the browser&amp;rsquo;s same-origin policy yet still occupy the same cookie site. A service at &lt;code&gt;accounts.example.com&lt;/code&gt; and another at &lt;code&gt;shop.example.com&lt;/code&gt; have different origins because their hosts differ, but cookie policy can classify their request context at a broader site boundary. That gap matters when &lt;code&gt;SameSite&lt;/code&gt; is treated as if it were equivalent to origin isolation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
