Reverse proxy
A reverse proxy is a server-side intermediary that receives client requests, forwards them to backend servers or services, and relays their responses.
ASP.NET Core in Action, 3e
A reverse proxy is a server that receives client requests and forwards them to backend applications or services on the clients' behalf.
- How it is used
- Positions a proxy between internet clients and ASP.NET Core applications to forward requests and support production hosting.
- How deep it goes
- Explains hosting tradeoffs and forwarded-header configuration, while limiting IIS setup to basic requirements and deferring exhaustive Linux proxy configuration.
- Examples
- Uses IIS and NGINX hosting scenarios and a forwarded-headers middleware configuration to illustrate deployment.
- What you can do after
- Operate/configure forwarded-header handling in ASP.NET Core and evaluate direct hosting against using a reverse proxy.
Read how ASP.NET Core in Action, 3e explains reverse proxy →
Learn Docker in a Month of Lunches, Second Edition
A reverse proxy is a server or service that receives client requests and forwards them to backend applications or services, often selecting a destination based on request attributes.
- How it is used
- Routes incoming HTTP traffic to multiple internal containerized applications through one gateway on standard ports.
- How deep it goes
- Works through nginx routing, HTTPS, load balancing, caching, and Traefik labels; stops short of nginx’s further compression and client-cache features.
- Examples
- Uses nginx site configurations, Traefik container labels, an image-gallery API, and a pi-calculation caching lab.
- What you can do after
- Operate/configure it with nginx or Traefik to route container traffic and test caching, HTTPS, or load balancing.
Read how Learn Docker in a Month of Lunches, Second Edition explains reverse proxy →
Kubernetes in Action, Second Edition
A reverse proxy is a server-side intermediary that receives client requests and forwards them to backend applications or services.
- How it is used
- Routes incoming external traffic to backend applications, often providing HTTPS or application-layer load balancing.
- How deep it goes
- Explains request routing, controller configuration, sidecar placement, and TLS termination, but not proxy implementation internals.
- Examples
- Uses Envoy sidecars, Kubernetes Ingress objects, TLS Secrets, wildcard certificates, and kiada, quote, and quiz services.
- What you can do after
- Configure HTTPS and external request routing through an Ingress reverse proxy without modifying backend application code.
Read how Kubernetes in Action, Second Edition explains reverse proxy →
Secure APIs
A reverse proxy receives client requests and forwards them to backend servers on the clients' behalf.
- How it is used
- Places reverse proxies at the internet boundary to channel inbound requests toward protected API services.
- How deep it goes
- Explains the network role and placement but stops short of implementation-specific proxy configuration.
- Examples
- Uses a DMZ request path that forwards traffic to private APIs while withholding internal and development endpoints.
- What you can do after
- Operate/configure inbound paths by placing reverse proxies in a DMZ and keeping backend services in private subnets.
Fundamentals of Cybersecurity
A reverse proxy is an intermediary server that receives client requests and forwards them to one or more backend servers.
- How it is used
- Routes incoming requests to an internal web server selected for workload.
- How deep it goes
- Describes server selection through a simple analogy without detailing proxy internals.
- Examples
- Uses a warehouse front desk assigning work to the least busy worker.
- What you can do after
- Understand how a reverse proxy directs requests to a less busy web server.
Read how Fundamentals of Cybersecurity explains reverse proxy →
Road to Kubernetes
A reverse proxy is a network intermediary that accepts client requests and forwards them to one or more backend servers or applications.
- How it is used
- Routes public web traffic to background Python and Node.js applications during manual virtual-machine deployment.
- How deep it goes
- Explains forwarding, URL locations, site enablement, default removal, and restart, while deferring advanced load-balancing details.
- Examples
- Uses NGINX locations mapping / to gunicorn on port 8888 and /js/ to Express on port 3000.
- What you can do after
- Operate/configure NGINX to expose multiple backend applications through URL paths and restart the service after enabling configuration.
Also covered in
- Building Web APIs with ASP.NET Core
- Go by Example
- Spring Microservices in Action
- Server-Side WebAssembly
What to know first
- HTTPHTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
- cachingCaching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
- load balancingLoad balancing is the distribution or adjustment of work across multiple resources to manage demand and reduce overload or imbalance.
- TLSTransport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
Related concepts
- zuul serverincludes · A Zuul server is a Zuul deployment configured without the built-in reverse proxy filters or Eureka-based service discovery.
- NGINXincludes · NGINX is open-source web-server and reverse-proxy software that serves HTTP content, forwards requests, and can load-balance network traffic.
- API gatewayincludes · An API gateway is a server-side intermediary that provides an entry point for client requests to backend APIs or services and routes or mediates those requests.
- serveruses · A server is a computer system or software process that provides data, resources, or services to other systems, typically by responding to requests.
- cachingalternative to · Caching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
Questions about reverse proxy
What is reverse proxy?
A reverse proxy is a server-side intermediary that receives client requests, forwards them to backend servers or services, and relays their responses.
Which Manning books explain reverse proxy?
ASP.NET Core in Action, 3e, Learn Docker in a Month of Lunches, Second Edition, Kubernetes in Action, Second Edition, Secure APIs, Fundamentals of Cybersecurity and Road to Kubernetes.
What should I know before learning reverse proxy?
Manning books that teach reverse proxy usually introduce HTTP, caching, load balancing and TLS first.
What is the difference between reverse proxy and caching?
A reverse proxy is a server-side intermediary that receives client requests, forwards them to backend servers or services, and relays their responses. Caching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
What kinds of reverse proxy are there?
Kinds of reverse proxy include zuul server, NGINX and API gateway.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





