<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nginx on toorun.dev</title><link>https://toorun.dev/tags/nginx/</link><description>Recent content in nginx on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 24 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is a Reverse Proxy? A Simple Beginner Guide with Docker and Nginx</title><link>https://toorun.dev/posts/what-is-a-reverse-proxy-a-simple-beginner-guide-with-docker-and-nginx/</link><pubDate>Sun, 24 May 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/what-is-a-reverse-proxy-a-simple-beginner-guide-with-docker-and-nginx/</guid><description>What Is a Reverse Proxy? If you are new to networking, a reverse proxy sounds more complex than it really is.
In very simple words:
A reverse proxy is a middle layer between your browser and an app. You talk to the reverse proxy first. The reverse proxy forwards your request to the real backend service. Then it sends the backend response back to you. So your browser does not talk directly to the backend.</description></item></channel></rss>