<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fetch Metadata on Nalar</title>
    <link>https://nalar.dev/tags/fetch-metadata/</link>
    <description>Recent content in Fetch Metadata on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/fetch-metadata/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fetch Metadata Makes Cross-Site Request Context Visible</title>
      <link>https://nalar.dev/fetch-metadata-makes-cross-site-request-context-visible/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/fetch-metadata-makes-cross-site-request-context-visible/</guid>
      <description>&lt;h1 id=&#34;fetch-metadata-makes-cross-site-request-context-visible&#34;&gt;Fetch Metadata Makes Cross-Site Request Context Visible&lt;/h1&gt;&#xA;&lt;p&gt;A server receiving an authenticated HTTP request often sees valid cookies, a plausible path, and a method that the application accepts. Those facts do not reveal whether the request began inside the application&amp;rsquo;s own page or was triggered by a document on another site. For endpoints that change state, that missing context has long been central to cross-site request forgery defenses.&lt;/p&gt;&#xA;&lt;p&gt;Fetch Metadata request headers expose part of the context already known to the browser. Headers such as &lt;code&gt;Sec-Fetch-Site&lt;/code&gt;, &lt;code&gt;Sec-Fetch-Mode&lt;/code&gt;, &lt;code&gt;Sec-Fetch-Dest&lt;/code&gt;, and &lt;code&gt;Sec-Fetch-User&lt;/code&gt; describe relationships and properties surrounding a request. A server can use those signals to reject request patterns that do not belong to its application architecture.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
