<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nginx on Junian Dev</title>
    <link>https://www.junian.dev/tags/nginx/</link>
    <description>Recent content in Nginx on Junian Dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>author@junian.dev (Junian Triajianto)</managingEditor>
    <webMaster>author@junian.dev (Junian Triajianto)</webMaster>
    <copyright>Copyright &amp;copy; 2014 - 2026 Junian.dev</copyright>
    
	    <atom:link href="https://www.junian.dev/tags/nginx/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>How to Allow Underscore Headers in Nginx</title>
      <link>https://www.junian.dev/dev/nginx-allow-underscore-header/</link>
      <pubDate>Sun, 28 Sep 2025 02:43:24 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/nginx-allow-underscore-header/</guid>
      <description>&lt;p&gt;Have you ever noticed that some HTTP request headers are missing when using Nginx?&lt;/p&gt;
&lt;p&gt;I experienced this issue myself. Headers containing underscores (such as &lt;code&gt;_Security_Token_&lt;/code&gt; or &lt;code&gt;_Device_ID_&lt;/code&gt;) were silently dropped by Nginx. This caused problems during mobile app testing, as token authentication kept failing.&lt;/p&gt;
&lt;p&gt;It turns out that HTTP headers with underscores are uncommon and generally discouraged when possible.&lt;/p&gt;
&lt;p&gt;The problem is, sometimes you don&amp;rsquo;t have control over how the upstream server works.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
