Forward proxy (client-side)
A forward proxy intercepts outbound requests from clients inside a network.
Forward proxy use cases
- Corporate egress — employees access the internet through a controlled gateway.
- Anonymity / geo bypass — client IP hidden from destination (VPN-like).
- Content filtering — block categories of sites on corporate networks.
- Caching — cache frequently requested external resources for many internal users.
[Laptop] → [Forward proxy] → [Internet] → [api.github.com]
(company policy,
logging, cache)
Clients must be configured to use the proxy (browser settings, HTTP_PROXY env var).
export HTTP_PROXY=http://proxy.corp.example:8080
export HTTPS_PROXY=http://proxy.corp.example:8080
curl https://api.github.com/user
# Request exits via proxy; GitHub sees proxy IP
Reverse proxy (server-side)
A reverse proxy accepts inbound traffic from the internet and forwards it to internal servers.
Forward
Forward proxyclient-side
Corporate firewall, VPN egress.
Reverse
Reverse proxyserver-side
Load balancing, TLS termination, caching.
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 5 sections
- Reverse proxy responsibilities
- NGINX reverse proxy example
- Forward vs reverse — side by side
- API gateway as reverse proxy++
- When to mention each in interviews
Test yourself
Answer these before moving on — recall is what makes it stick.