<?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 Headers on Nalar</title>
    <link>https://nalar.dev/tags/http-security-headers/</link>
    <description>Recent content in HTTP Security Headers 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/http-security-headers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforce HTTPS with HTTP Strict Transport Security</title>
      <link>https://nalar.dev/enforce-https-with-http-strict-transport-security/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/enforce-https-with-http-strict-transport-security/</guid>
      <description>&lt;p&gt;TLS protects an HTTP connection after the browser has chosen HTTPS and completed certificate validation. A separate problem exists before that protected connection begins: a user can type a bare hostname, follow an old HTTP link, or reach a page that redirects from HTTP to HTTPS.&lt;/p&gt;&#xA;&lt;p&gt;HTTP Strict Transport Security, usually called HSTS, lets a site tell supporting browsers to treat future connections to that host as HTTPS-only. The browser stores the policy for a defined period. While the policy is active, an HTTP navigation is upgraded locally before an insecure HTTP request is sent.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
