What is a reverse proxy?
Definition
A proxy deployed in front of a server. Clients connect to it as if it were the origin, and it forwards to the real backend.
RFC 9110 has an older name for it: a gateway, “a.k.a. reverse proxy”, an intermediary that “acts as an origin server” toward the client while forwarding requests to the servers behind it. Nginx, HAProxy, Varnish, Cloudflare, Fastly, Akamai and CloudFront all do this job. Operators use one to spread load across backends, to terminate TLS in one place, to cache, and to filter traffic before it costs the application anything.
For anyone collecting data, that last job is the one that matters. On a large site, the machine that decides whether your request succeeds is usually the reverse proxy, not the application. A block that arrives almost instantly, or an error page that looks nothing like the site, usually came from the edge.
Seeing the layer from outside
Reverse proxies often name themselves in response headers. This is the check we ran:
for h in www.cloudflare.com www.fastly.com aws.amazon.com www.bbc.co.uk \
www.reddit.com en.wikipedia.org www.akamai.com github.com; do
echo "== $h"
curl -sI --max-time 15 "https://$h/" \
| grep -iE '^(HTTP|server|via|x-cache|x-served-by|cf-ray|x-amz-cf-pop|akamai-grn)'
done
We ran that loop with curl 8.7.1 on 21 October 2026, twice, thirteen minutes apart, from one connection in Europe: a bare HEAD request to each of eight well-known sites, no cookies, no custom headers. Both runs returned the same statuses and the same header names. Values that identify a specific cache node or counter have been shortened.
| Site | Status | Headers that name an intermediary | What they point to |
|---|---|---|---|
| www.cloudflare.com | 103, then 200 | server: cloudflare, cf-ray |
Cloudflare’s edge |
| www.fastly.com | 200 | x-served-by with two cache nodes, x-cache: HIT, HIT |
Two Fastly cache layers; the server header held a custom string |
| aws.amazon.com | 200 | via: 1.1 ….cloudfront.net (CloudFront), x-amz-cf-pop |
CloudFront |
| www.bbc.co.uk | 200 | via: 1.1 BBC-GTM, 1.1 Belfrage, 1.1 varnish |
Three intermediaries named in order, plus an x-served-by cache node |
| www.reddit.com | 200 | via: 1.1 varnish |
A Varnish cache |
| en.wikipedia.org | 301 | x-cache: cp3070 miss, cp3070 hit/… |
Wikimedia’s own cache servers |
| www.akamai.com | 403 | Akamai-GRN |
Akamai’s edge refused the request |
| github.com | 200 | server: github.com |
Nothing third-party named |
Two rows reward a closer look. The BBC’s Via header lists three hops in order, which is how RFC 9110 defines the field: each intermediary appends its own entry, so it reads as a path. It is not the whole path. The same response carried req-svc-chain: FASTLY,GTM,BELFRAGE,WEBCORE, naming a Fastly layer that Via leaves out. The standard allows that: a gateway must add itself to requests it forwards, but on responses it may stay silent. And www.akamai.com answered our plain curl HEAD with HTTP/1.1 403 Forbidden and an Akamai reference header. Nothing about the URL was wrong. The edge judged the client and refused it before the site’s own servers were involved.
Run the same loop through your proxy, adding the -x flag from the curl guide, and compare. An edge that answers your direct request with 200 and your proxied one with 403 has judged the exit address, not the URL.
Absence proves nothing. github.com named no CDN, but many operators strip or rewrite these headers on purpose. A missing Via is not evidence that no reverse proxy exists.
What changes when you know it is there
A refusal from the edge means the request never reached the application, so changing the path or the query rarely helps. What the edge evaluates is the client: the address and its network, the TLS handshake, the header set and its order. The study What HTTP clients send before you configure anything shows how far a default library request sits from a browser’s, which is the gap these edges measure. The guide 403 vs 407 vs 429 separates a block from the edge from a failure at your own proxy, which is the first thing to settle when requests start failing.
What it passes to the origin
The reverse proxy also decides what the origin learns about you. It usually passes your address inward in X-Forwarded-For or the standard Forwarded header defined in RFC 7239, because otherwise every request would appear to come from the proxy itself. If you are on a forward proxy too, the origin may see a chain: the edge records the proxy’s exit address, not yours.
Many reverse proxies also pin each visitor to one backend so in-memory session data survives. That is the load-balancing meaning of a sticky session. Where the affinity is keyed on the client’s address rather than a cookie, it also explains why changing your exit address mid-visit can log you out of some sites and not others.
Frequently asked questions
Why does a reverse proxy matter if I only read public pages?
Can I tell which reverse proxy a site uses?
What is the difference between a forward proxy and a reverse proxy?
Sources
Also covered in
- Forward and reverse proxiesin What is a proxy server and how does it work?