<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Http on The Coders Blog</title><link>https://thecodersblog.com/tag/http/</link><description>Recent content in Http on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Apr 2026 16:54:36 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/http/index.xml" rel="self" type="application/rss+xml"/><item><title>FastCGI's Enduring Edge: Why the 30-Year-Old Protocol Still Dominates Reverse Proxies in 2026</title><link>https://thecodersblog.com/fastcgi-the-underestimated-protocol-for-modern-reverse-proxies-2026/</link><pubDate>Wed, 29 Apr 2026 16:54:36 +0000</pubDate><guid>https://thecodersblog.com/fastcgi-the-underestimated-protocol-for-modern-reverse-proxies-2026/</guid><description>&lt;p&gt;Your carefully optimized microservice architecture might be bleeding performance and opening critical vulnerabilities at its very core – and the culprit isn&amp;rsquo;t what you think: it&amp;rsquo;s HTTP between your reverse proxy and backend services. This isn&amp;rsquo;t a theoretical threat; it&amp;rsquo;s a persistent, real-world issue, and it&amp;rsquo;s time to address it with a proven solution that has been quietly outperforming modern alternatives for three decades.&lt;/p&gt;
&lt;h3 id="the-core-problem-why-http-fails-for-internal-proxy-to-backend-communication"&gt;The Core Problem: Why HTTP Fails for Internal Proxy-to-Backend Communication&lt;/h3&gt;
&lt;p&gt;HTTP, while the undisputed champion for client-facing requests, is a poor choice for trusted, internal communication between a reverse proxy and its backend services. Its inherent &lt;strong&gt;statelessness&lt;/strong&gt; and &lt;strong&gt;extensive header parsing&lt;/strong&gt; introduce significant overhead and latency where they are least welcome. Every request, even from a trusted proxy, demands a full parsing of headers, cookies, and other metadata, leading to unnecessary CPU cycles and memory consumption on your critical backend services.&lt;/p&gt;</description></item><item><title>FastCGI's Enduring Edge: Why the 30-Year-Old Protocol Still Dominates Reverse Proxies in 2026</title><link>https://thecodersblog.com/fastcgi-the-underestimated-protocol-for-modern-reverse-proxies-2026/</link><pubDate>Wed, 29 Apr 2026 16:54:36 +0000</pubDate><guid>https://thecodersblog.com/fastcgi-the-underestimated-protocol-for-modern-reverse-proxies-2026/</guid><description>&lt;p&gt;Your carefully optimized microservice architecture might be bleeding performance and opening critical vulnerabilities at its very core – and the culprit isn&amp;rsquo;t what you think: it&amp;rsquo;s HTTP between your reverse proxy and backend services. This isn&amp;rsquo;t a theoretical threat; it&amp;rsquo;s a persistent, real-world issue, and it&amp;rsquo;s time to address it with a proven solution that has been quietly outperforming modern alternatives for three decades.&lt;/p&gt;
&lt;h3 id="the-core-problem-why-http-fails-for-internal-proxy-to-backend-communication"&gt;The Core Problem: Why HTTP Fails for Internal Proxy-to-Backend Communication&lt;/h3&gt;
&lt;p&gt;HTTP, while the undisputed champion for client-facing requests, is a poor choice for trusted, internal communication between a reverse proxy and its backend services. Its inherent &lt;strong&gt;statelessness&lt;/strong&gt; and &lt;strong&gt;extensive header parsing&lt;/strong&gt; introduce significant overhead and latency where they are least welcome. Every request, even from a trusted proxy, demands a full parsing of headers, cookies, and other metadata, leading to unnecessary CPU cycles and memory consumption on your critical backend services.&lt;/p&gt;</description></item><item><title>Custom Header Naming Convention in HTTP: Best Practices and Conventions</title><link>https://thecodersblog.com/custom-header-naming-convention-http-practices-conventions/</link><pubDate>Tue, 06 Jun 2023 05:25:02 +0000</pubDate><guid>https://thecodersblog.com/custom-header-naming-convention-http-practices-conventions/</guid><description>&lt;p&gt;HTTP headers are the unsung heroes of web communication, carrying crucial metadata that powers everything from authentication to caching. While standard headers like &lt;code&gt;Content-Type&lt;/code&gt; and &lt;code&gt;Authorization&lt;/code&gt; are well-established, modern applications often require custom headers to transmit application-specific data. But here&amp;rsquo;s the challenge: &lt;strong&gt;poor header naming can break APIs, confuse developers, and create security vulnerabilities&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In 2025, with the rise of microservices, GraphQL, and edge computing, proper header naming has become more critical than ever. This comprehensive guide explores modern HTTP header naming conventions, the evolution beyond the deprecated &amp;ldquo;X-&amp;rdquo; prefix, and battle-tested practices from leading tech companies.&lt;/p&gt;</description></item></channel></rss>