Forward Proxy vs Reverse Proxy

What a Proxy Server Does, in General

A proxy server sits between a client and a destination, forwarding requests on the client's behalf rather than the client connecting directly - the destination sees the proxy, not the original requester.

Forward Proxy: Representing the Client

Client ----> [ Forward Proxy ] ----> Internet / Destination Server

A forward proxy sits in front of clients, forwarding their outgoing requests to the internet. From the destination server's perspective, the request appears to come from the proxy, not from the original client - commonly used by organizations to filter, monitor, or control employees' outbound internet traffic.

Reverse Proxy: Representing the Server

Client ----> [ Reverse Proxy ] ----> Backend Server(s)

A reverse proxy sits in front of one or more servers, receiving incoming client requests and forwarding them to the actual backend server(s). From the client's perspective, they're simply talking to "the website" - they have no visibility into how many actual servers exist behind that reverse proxy.

The Core Distinction: Whose Side Is It On?

How This Connects to Load Balancing

A reverse proxy is closely related to (and often implemented as part of) the load balancing concept covered earlier in this project - many real-world load balancers are, technically speaking, a specific and common application of reverse proxying.