<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Host Validation on Nalar</title>
    <link>https://nalar.dev/tags/host-validation/</link>
    <description>Recent content in Host Validation on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/host-validation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Validate Host Authority Before Trusting Request Metadata</title>
      <link>https://nalar.dev/validate-host-authority-before-trusting-request-metadata/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/validate-host-authority-before-trusting-request-metadata/</guid>
      <description>&lt;p&gt;HTTP applications often need to know which host a client intended to reach. Frameworks expose that value through fields such as &lt;code&gt;Host&lt;/code&gt;, &lt;code&gt;request.host&lt;/code&gt;, or a parsed request authority. It can look like infrastructure metadata, but at an application boundary it is commonly influenced by the client.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters when an application uses the value for security-sensitive work. A hostile authority can affect absolute links, redirects, cache entries, tenant selection, origin checks, or routing decisions if the application accepts it without a trust policy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
