<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse-Proxy on Danilo Falcão da Silva</title><link>https://falcao.org/tags/reverse-proxy/</link><description>Recent content in Reverse-Proxy on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 17:35:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/reverse-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>Caddy, Nginx, Traefik: Picking a Reverse Proxy in 2026</title><link>https://falcao.org/posts/caddy-nginx-traefik-2026/</link><pubDate>Wed, 20 May 2026 17:35:00 -0300</pubDate><guid>https://falcao.org/posts/caddy-nginx-traefik-2026/</guid><description>&lt;p>There is a kind of infrastructure question that never really gets
settled, just re-litigated every couple of years as the surrounding
ecosystem moves. &lt;strong>&amp;ldquo;Which reverse proxy?&amp;rdquo;&lt;/strong> is one of those questions.&lt;/p>
&lt;p>The shortlist hasn&amp;rsquo;t changed much: &lt;strong>Caddy&lt;/strong>, &lt;strong>Nginx&lt;/strong>, &lt;strong>Traefik&lt;/strong>.
The context around them has changed a lot. The community &lt;code>ingress-nginx&lt;/code>
project reached end-of-life in &lt;strong>March 2026&lt;/strong>. &lt;strong>RKE2 v1.36&lt;/strong> flipped
to &lt;strong>Traefik&lt;/strong> as the default ingress. Caddy quietly shipped &lt;strong>2.11&lt;/strong>
with better health-checking and ECH rotation. Nginx is on &lt;strong>1.31
mainline / 1.30.1 stable&lt;/strong> and treats HTTP/3 as a first-class but
still-evolving feature.&lt;/p></description></item></channel></rss>