<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Referrer Policy on Nalar</title>
    <link>https://nalar.dev/tags/referrer-policy/</link>
    <description>Recent content in Referrer Policy on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/referrer-policy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Referrer Policy Controls Navigation Metadata Exposure</title>
      <link>https://nalar.dev/referrer-policy-controls-navigation-metadata-exposure/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/referrer-policy-controls-navigation-metadata-exposure/</guid>
      <description>&lt;h1 id=&#34;referrer-policy-controls-navigation-metadata-exposure&#34;&gt;Referrer Policy Controls Navigation Metadata Exposure&lt;/h1&gt;&#xA;&lt;p&gt;A link from an internal account page to an external support site can carry more context than the destination needs. Depending on browser policy and request conditions, the HTTP &lt;code&gt;Referer&lt;/code&gt; header can identify the source origin or include a fuller source address. If that address contains sensitive path structure or query data, navigation metadata becomes an unintended disclosure channel.&lt;/p&gt;&#xA;&lt;p&gt;Referrer Policy gives a document, response, or individual element control over how much source address information accompanies eligible requests. It does not encrypt traffic, authenticate destinations, or prevent navigation. Its purpose is narrower: constrain the referrer information exposed when the browser makes requests.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
