Protocol ExplorerGuidesPricing

Reverse Proxy: Routing Requests to Upstream Servers

A reverse proxy sits in front of one or more servers and receives requests on their behalf. It is an architecture pattern implemented using HTTP and network components, not a separate wire protocol.

Updated · Editorial approach and simulation limits

Inbound proxying and upstream selection

A client connects to the reverse proxy’s public endpoint. The proxy selects an upstream server using host name, path, headers, health state or configured policy, then forwards the request and returns the response. The client may see a single service address even when many backend servers handle traffic.

Load balancing, access control, caching and request routing are common reverse-proxy functions. The exact behavior comes from the proxy configuration and application contract; the phrase reverse proxy does not specify one standard algorithm.

TLS termination changes the observation points

A proxy can terminate TLS and establish a separate connection to an upstream server, or it can pass encrypted traffic through. If it terminates TLS, it can read and modify HTTP at that boundary, subject to its configuration. If it only tunnels the connection, it cannot inspect protected application content.

A trace from the client side and a trace from the backend side can show different addresses, TLS sessions and timing. Correlate request IDs and proxy logs before comparing timestamps or assuming that a backend generated the client-visible response.

Forward and reverse proxies face opposite traffic directions

A forward proxy is selected by a client and makes outbound requests on the client’s behalf. A reverse proxy is selected by service operators and receives inbound requests for servers. Both can speak HTTP, but their trust boundaries and configuration differ.

When troubleshooting, identify which host the client connected to, whether TLS ended there, and which upstream received the request. Protocol Explorer’s diagram models that path; it does not route traffic through a proxy.

Explore Reverse Proxy interactively

Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.

Open the Reverse Proxy animation · Compare Free and Pro

Specification and source

For exact protocol requirements, consult the primary document: RFC 9110: HTTP Semantics. This page summarizes selected behavior and is not a substitute for the specification.

Related protocol lessons

Browse all application protocols · Follow a web request across intermediary layers