<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HTTP Cookies on Nalar</title>
    <link>https://nalar.dev/tags/http-cookies/</link>
    <description>Recent content in HTTP Cookies on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/http-cookies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cookie Prefixes Bind Browser-Enforced Constraints to Cookie Names</title>
      <link>https://nalar.dev/cookie-prefixes-bind-browser-enforced-constraints-to-cookie-names/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/cookie-prefixes-bind-browser-enforced-constraints-to-cookie-names/</guid>
      <description>&lt;h1 id=&#34;cookie-prefixes-bind-browser-enforced-constraints-to-cookie-names&#34;&gt;Cookie Prefixes Bind Browser-Enforced Constraints to Cookie Names&lt;/h1&gt;&#xA;&lt;p&gt;HTTP cookies carry security attributes such as &lt;code&gt;Secure&lt;/code&gt;, &lt;code&gt;HttpOnly&lt;/code&gt;, &lt;code&gt;Domain&lt;/code&gt;, and &lt;code&gt;Path&lt;/code&gt;. Cookie prefixes add another layer: a reserved pattern in the cookie name tells a supporting browser that specific attributes must accompany the cookie. If the &lt;code&gt;Set-Cookie&lt;/code&gt; header violates that contract, the browser rejects the cookie instead of storing it under weaker settings.&lt;/p&gt;&#xA;&lt;p&gt;This mechanism is useful because configuration intent becomes visible in the name itself. A session cookie named with a host-bound prefix cannot silently drift into a domain-scoped cookie without failing the browser&amp;rsquo;s prefix checks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
