<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HTTP Security on Nalar</title>
    <link>https://nalar.dev/tags/http-security/</link>
    <description>Recent content in HTTP Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/http-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Control Referrer Data with Referrer-Policy</title>
      <link>https://nalar.dev/control-referrer-data-with-referrer-policy/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/control-referrer-data-with-referrer-policy/</guid>
      <description>&lt;p&gt;A browser can attach source-page information to an outbound request through the HTTP &lt;code&gt;Referer&lt;/code&gt; header. That context can help with analytics, navigation flows, and abuse detection, but it can also expose more URL data than a destination needs.&lt;/p&gt;&#xA;&lt;p&gt;An explicit &lt;code&gt;Referrer-Policy&lt;/code&gt; gives a site control over this boundary. The main security objective is simple: &lt;strong&gt;send the minimum source context needed for legitimate behavior, especially when a request crosses to another origin&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reject Ambiguous HTTP Message Framing</title>
      <link>https://nalar.dev/reject-ambiguous-http-message-framing/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/reject-ambiguous-http-message-framing/</guid>
      <description>&lt;p&gt;Modern web requests often cross several HTTP-speaking components before reaching application code. A request may pass through a CDN, load balancer, reverse proxy, API gateway, service mesh, and application server. Each component must agree on exactly where one request ends and the next begins.&lt;/p&gt;&#xA;&lt;p&gt;If two components interpret message boundaries differently, bytes that one component treats as part of a request can become a second request for another component. This parser disagreement is the foundation of HTTP request smuggling.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
