<?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/tags/reverse-proxy/</link><description>Recent content in Reverse Proxy on wid's blog</description><generator>Hugo</generator><language>ko</language><lastBuildDate>Wed, 10 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/tags/reverse-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>Envoy — 정적 reverse proxy가 cloud-native에서 마주친 한계</title><link>https://wid-blog.github.io/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/posts/tech/infra/envoy-and-l7-dynamic-proxy/</guid><description>수동 reload, 정적 upstream, 빈약한 L7 observability — 정적 reverse proxy가 cloud-native 환경에서 마주친 한계를 Envoy의 xDS와 filter chain이 어떻게 푸는지 정리한다.</description></item><item><title>Web Server, WAS, Reverse Proxy — 각자 다른 문제를 푼다</title><link>https://wid-blog.github.io/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/posts/tech/infra/web-server-was-reverse-proxy/</guid><description>세 도구는 같은 자리에 보이지만 풀어내는 문제가 다르다. 정적 컨텐츠 전달, 동적 컨텐츠 생성, 트래픽 중개를 어떻게 나눠 갖는지 정리한다.</description></item></channel></rss>