The difference between a forward vs reverse proxy comes down to who the proxy works for. A forward proxy acts on behalf of clients: it takes your request and sends it out to the internet, so websites see the proxy instead of you. A reverse proxy acts on behalf of servers: it receives requests from the internet and passes them to backend servers, so visitors see the proxy instead of the backend. The plumbing is similar; the purpose is opposite.
What a Forward Proxy Does
A forward proxy is configured on the client side. Your browser, script or app knows it's using a proxy and sends requests to it explicitly. The proxy then connects to whatever destination you asked for.
- It hides the client: destinations see the proxy's IP.
- The client chooses to use it, with a setting like -x in curl or proxies= in Python.
- It can reach any site; the destination doesn't know or care that a proxy is involved.
- Typical uses: corporate outbound filtering, caching, web scraping, geo-testing, routing through residential or mobile IPs.
Every commercial proxy service, including NodeProxies, is a forward proxy. When you send traffic to global.nodeproxies.xyz:8080, the gateway forwards it out through a residential, mobile or datacenter IP. If you're new to this, start with what a proxy server is.
# A forward proxy: the client opts in
curl -x http://USERNAME:[email protected]:8080 https://example.comWhat a Reverse Proxy Does
A reverse proxy is configured on the server side. Visitors don't know it exists: they type example.com, DNS points to the reverse proxy, and it decides which backend handles the request.
- It hides the servers: visitors see the proxy's IP and never connect to backends directly.
- The site owner sets it up; clients need no configuration.
- It only serves the sites it's configured for.
- Typical uses: TLS termination, load balancing, caching static files, compression, rate limiting, web application firewalls, DDoS absorption.
A minimal nginx reverse proxy in front of an app running on port 3000 looks like this:
server {
listen 80;
server_name example.com;
location / {
proxy_pass http://127.0.0.1:3000;
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;
}
}Notice the X-Forwarded-For header. A reverse proxy passes the visitor's IP to the backend on purpose, because the app needs it for logs and rate limits. A privacy-focused forward proxy does the opposite and strips any header that would reveal the client.
Forward vs Reverse Proxy: Side by Side
- Works for: forward = the client; reverse = the server.
- Configured by: forward = the user or their tool; reverse = the site operator.
- Hides: forward = the client's IP; reverse = the backend servers' IPs.
- Destinations: forward = any site; reverse = only its own sites.
- Client awareness: forward = the client knows; reverse = the client usually doesn't.
- Common software: forward = Squid, commercial proxy gateways; reverse = nginx, HAProxy, Caddy, CDN edges.
Where They Meet: Scraping a Site Behind a CDN
In real traffic the two often sit on the same path. When your scraper fetches a page through a residential proxy, the request goes: your code, then the forward proxy, then the site's reverse proxy or CDN edge, then the origin server. The reverse proxy is usually where bot detection runs. It looks at the IP the forward proxy presents, its reputation and its network type, along with your TLS and HTTP fingerprint.
That's why the kind of forward proxy matters. A datacenter IP arriving at a protected reverse proxy is often challenged straight away, while a residential IP looks like a normal visitor. Our posts on IP reputation and why proxies get blocked go deeper.
Is a Load Balancer a Reverse Proxy?
A layer-7 load balancer that terminates HTTP and picks a backend per request is a reverse proxy. A layer-4 load balancer that forwards TCP packets without understanding HTTP is closer to a router, though people often call both reverse proxies. A CDN is a distributed reverse proxy with caching.
Is a VPN a Forward Proxy?
Functionally it plays a similar role, since it relays client traffic and hides the client IP, but it works at the network layer for the whole device rather than per application. See proxy vs VPN.
Using a Forward Proxy With NodeProxies
If you need a forward proxy with residential, mobile or datacenter exits, NodeProxies gives you one gateway for all of them. Put the country in the username (USERNAME-country-gb), or add -session-{id}-time-{minutes} to keep the same IP. Register, add balance from $3, and compare per-GB rates on pricing. API details are in the docs.
FAQ
Is nginx a forward or reverse proxy?
nginx is almost always used as a reverse proxy. It can't handle HTTPS CONNECT tunnels without third-party modules, so it's a poor general-purpose forward proxy.
Is a residential proxy a forward proxy?
Yes. It acts for you, the client, and makes the destination see a residential IP instead of yours.
Why is it called a reverse proxy?
Because the direction is reversed: instead of relaying outbound requests for clients, it relays inbound requests for servers.
Can one server be both a forward and reverse proxy?
Software like Squid or HAProxy can be configured either way, but in practice you run them as separate roles with separate configs and access rules.
