<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Trust Boundary on Nalar</title>
    <link>https://nalar.dev/tags/trust-boundary/</link>
    <description>Recent content in Trust Boundary on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/trust-boundary/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Trust Forwarded Headers Only from Known Proxies</title>
      <link>https://nalar.dev/trust-forwarded-headers-only-from-known-proxies/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/trust-forwarded-headers-only-from-known-proxies/</guid>
      <description>&lt;h1 id=&#34;trust-forwarded-headers-only-from-known-proxies&#34;&gt;Trust Forwarded Headers Only from Known Proxies&lt;/h1&gt;&#xA;&lt;p&gt;A reverse proxy often knows facts that an application server cannot observe directly. It may terminate TLS, accept the public hostname, and receive the client connection before opening a separate connection to the backend. Forwarding fields carry those facts across the second hop.&lt;/p&gt;&#xA;&lt;p&gt;That arrangement is safe only when the backend can distinguish proxy-supplied metadata from client-supplied HTTP fields. A header name does not create trust. The trust comes from the network path, the proxy configuration, and a rule that defines which hop may set or replace each field.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
