<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>反向代理 on Text Matrix</title><link>https://txtmix.com/tags/%E5%8F%8D%E5%90%91%E4%BB%A3%E7%90%86/</link><description>Recent content in 反向代理 on Text Matrix</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Tue, 21 Jul 2026 20:06:14 +0800</lastBuildDate><atom:link href="https://txtmix.com/tags/%E5%8F%8D%E5%90%91%E4%BB%A3%E7%90%86/index.xml" rel="self" type="application/rss+xml"/><item><title>Nginx 1.31 安全修复与现代部署：30 岁反向代理的常青之道</title><link>https://txtmix.com/posts/tech/nginx-1-31-security-and-modern-deployment/</link><pubDate>Sun, 07 Jun 2026 12:56:00 +0800</pubDate><guid>https://txtmix.com/posts/tech/nginx-1-31-security-and-modern-deployment/</guid><description>&lt;h1 id="nginx-131-安全修复与现代部署30-岁反向代理的常青之道">Nginx 1.31 安全修复与现代部署：30 岁反向代理的常青之道&lt;/h1>
&lt;blockquote>
&lt;p>&lt;strong>目标读者&lt;/strong>：运维 / SRE；架构师；评估 API gateway / 反向代理方案的人
&lt;strong>核心问题&lt;/strong>：Nginx 1.31.1 修复了哪些安全问题？在容器化、Kubernetes、Service Mesh 时代，Nginx 还有什么不可替代的位置？
&lt;strong>难度&lt;/strong>：⭐⭐（中级）
&lt;strong>来源&lt;/strong>：&lt;a href="https://nginx.org/" target="_blank" rel="noopener noreffer ">Nginx 官方公告&lt;/a> + &lt;a href="https://github.com/nginx/nginx" target="_blank" rel="noopener noreffer ">nginx/nginx&lt;/a>，30k+ ★ / BSD-2-Clause / 2026-06-07&lt;/p></description></item></channel></rss>