Reverse Proxy #

Reverse proxying is one of Nginx’s most common — and most powerful — uses in production environments. Almost every modern web application places Nginx in front of its application servers: Node.js, Python, PHP, Ruby, Go — to handle SSL termination, load balancing, caching, and various infrastructure needs before requests touch the application code.

Understanding how reverse proxying works in Nginx is the key to building efficient, secure, and scalable web architecture.

Learning Map #

flowchart TD
    A["🔀 Reverse Proxy Concepts\nForward vs Reverse,\nwhy production needs this"] --> B["📡 proxy_pass\nTrailing slash, Unix socket,\nWebSocket, path rewriting"]
    B --> C["📋 Proxy Headers\nX-Real-IP, X-Forwarded-For,\nadd_header inheritance trap"]
    C --> D["⏱ Buffering & Timeouts\nBuffering modes, 5 timeout types,\nkeepalive pool, error diagnosis"]
    D --> E["💾 Proxy Cache\nCache zone, cache key,\nbypass strategy, stale cache"]

Articles in This Section #

Article	What You’ll Learn
Reverse Proxy Concepts	The difference between forward and reverse proxies, why almost all production applications use them, the two-separate-connections request flow, and default header modifications
proxy_pass	The core reverse proxy directive — the critical trailing slash difference, proxying to Unix sockets, WebSocket, path rewriting, and complete configuration
Proxy Headers	How Nginx modifies headers by default, `proxy_set_header`, `proxy_hide_header`, `add_header` for responses, and the inheritance trap you must understand
Buffering & Timeouts	How buffering works, configuring the 5 timeout types, keepalive pools to the backend, tuning for streaming vs APIs, and reading error codes
Proxy Cache	Defining cache zones, cache keys, bypass strategies for authenticated users, stale cache when the backend errors, and how to purge cache