aoitcloud

Guides and How Tos

What Is a Reverse Proxy and Why Do Sites Use One?

A plain-English guide to reverse proxies: what they do, how they differ from a forward proxy, and why they sit in front of almost every modern website.

18 November 2026 5 min read

What Is a Reverse Proxy and Why Do Sites Use One? — AOIT Cloud knowledge base

If you have ever looked at a website’s server headers and seen “nginx” or “cloudflare” listed even though the site is built on something else entirely, you have already met a reverse proxy. It is one of those pieces of infrastructure that quietly does a lot of work without ever being the star of the show. This post explains what a reverse proxy actually is, how it differs from a forward proxy, and why so many websites run one.

What a reverse proxy actually does

A reverse proxy is a server that sits in front of one or more backend servers and intercepts requests on their behalf. When a visitor’s browser makes a request, it connects to the reverse proxy, not directly to the application server. The proxy decides what to do with that request, usually forwarding it to whichever backend server should handle it, then takes the response from that backend and sends it back to the visitor as though the proxy itself had produced it.

From the visitor’s point of view, there is only ever one server: the reverse proxy. They never see or need to know how many actual backend machines are working behind it, what software each one runs, or how requests are being distributed between them.

Reverse proxy versus forward proxy

It is easy to confuse a reverse proxy with a plain “forward proxy,” since both sit in the middle of a connection. The difference comes down to whose interests the proxy is acting for.

  • A forward proxy acts on behalf of clients. It sits in front of a group of users (for example, everyone on an office network) and forwards their requests out to the wider internet, often for filtering, caching, or privacy reasons. The destination server sees the proxy, not the individual client.
  • A reverse proxy acts on behalf of servers. It sits in front of one or more backend servers and forwards incoming requests to them, hiding the backend from the client. The client sees the proxy, not the individual backend server.

Put simply: a forward proxy protects and represents clients, a reverse proxy protects and represents servers.

Common real-world uses

Reverse proxies turn up in most modern web setups because they solve several practical problems at once.

  • Load balancing. The proxy can spread incoming requests across several identical backend servers, so no single machine gets overwhelmed and traffic keeps flowing even if one backend goes down. Running that kind of multi-server setup is exactly where Managed Cloud Hosting earns its keep.
  • SSL/TLS termination. The proxy can handle the encryption and decryption of HTTPS traffic itself, passing plain HTTP through to the backend servers. This centralises certificate management in one place instead of configuring TLS on every backend, using SSL certificates installed on the proxy rather than on each server behind it.
  • Caching. The proxy can store copies of frequently requested content and serve it directly, reducing load on the backend and speeding up responses. It’s the same principle a CDN uses at a larger, geographically distributed scale.
  • Hiding backend architecture. Because visitors only ever talk to the proxy, the internal layout, server software, and even the number of backend machines stay invisible from the outside, which is useful for both security and flexibility when changing infrastructure later.
  • Running multiple applications behind one IP address. A single reverse proxy can inspect the hostname in each incoming request and route it to a different application or backend accordingly, which is how one physical server (or one IP address) can serve several completely separate websites or apps, something a VPS makes straightforward when you’re hosting more than one site yourself.

A simple example

Nginx and Apache are the two software packages most commonly used as reverse proxies. A minimal Nginx configuration that forwards requests to an application running on the same machine, on port 8080, looks like this:

server {
    listen 80;
    server_name example.co.uk;

    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

The proxy_pass line tells Nginx where to forward the request. The proxy_set_header lines add extra headers so the backend application still knows the original hostname and the visitor’s real IP address, since as far as the raw network connection is concerned, the request is now coming from the proxy itself.

Summary

A reverse proxy sits in front of your backend servers, taking requests from clients and forwarding them on before returning the response as its own. Unlike a forward proxy, which represents clients to the outside world, a reverse proxy represents servers to the outside world. It is the piece of software behind load balancing, SSL termination, caching, hiding your backend setup, and running multiple sites from a single IP address, and it is why the server your browser talks to is often not the server actually generating the page.

Get in touch

Drop our team a message today