<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Reverse Proxy on wid's blog</title><link>https://wid-blog.github.io/en/tags/reverse-proxy/</link><description>Recent content in Reverse Proxy on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/reverse-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>Envoy — When Static Reverse Proxies Meet Cloud-Native</title><link>https://wid-blog.github.io/en/posts/tech/infra/envoy-and-l7-dynamic-proxy/</link><pubDate>Wed, 10 Jul 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/infra/envoy-and-l7-dynamic-proxy/</guid><description>Manual reload, static upstreams, weak L7 observability — four limits a static reverse proxy hits in a cloud-native environment, and the four mechanisms Envoy uses to address them.</description></item><item><title>Web Server, WAS, Reverse Proxy — Three Different Problems</title><link>https://wid-blog.github.io/en/posts/tech/infra/web-server-was-reverse-proxy/</link><pubDate>Sat, 15 Jun 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/infra/web-server-was-reverse-proxy/</guid><description>These three tools often sit in the same place but solve different problems. A look at how static content, dynamic content, and traffic mediation get split among them.</description></item></channel></rss>