reverse proxy
A server that receives requests on behalf of other servers and forwards them, returning their responses as if they were its own.
In more detail
A good proxy is boring: it forwards method, headers, status and body deliberately, sets timeouts, never blindly retries non-idempotent requests, and records the upstream result. Caches, load balancers and gateways are all kinds of proxy.
Examples
It can terminate TLS, add headers, cache responses and balance load across origins, and it hides the origins from clients. nginx and HAProxy are common ones. Inspect both the client-to-proxy and proxy-to-origin legs when something fails.mode=rev listen=443 origin=app tls=proxy has the proxy listening on 443 and terminating TLS.Related terms
- API gateway — A server that sits in front of one or more services and handles shared concerns such as routing, authentication, rate limits and TLS for every request.
- load balancer — A server that spreads incoming requests across several copies of a service so no single copy is overloaded.
- intermediary — Any program or device between client and server that handles traffic, such as a proxy, cache, load balancer, gateway or firewall.
- upstream and downstream — Relative positions in a chain of calls: from a proxy’s point of view the service it forwards to is upstream, and work that happens later as a result is downstream.
- forwarded headers — HTTP headers such as X-Forwarded-For that a proxy adds to tell the app the original client address and scheme.
- load balancing — Spreading requests or connections across several backend servers so no single one is overloaded and failed ones can be avoided.
- Kestrel — The cross-platform web server built into ASP.NET Core that listens for HTTP requests and hands them to your application.
- Ingress controller — The reverse proxy running in a Kubernetes cluster that reads Ingress rules and routes incoming traffic accordingly.
- heartbeat — A small message sent at regular intervals on a long-lived connection to prove that both ends and the path between them are still alive.
- proxy server — A server that sits between clients and servers and forwards requests on someone's behalf, often applying policy, caching or security on the way.
- origin server — The server that actually holds the content or runs the application, as opposed to a proxy or cache in front of it.
- TLS termination — Ending an encrypted TLS connection at a proxy or gateway, which decrypts the traffic and forwards it on to the service.
- cache — A store of earlier answers kept close to where they are needed so they can be reused instead of fetched or computed again.
Taught in
- HTTP Methods And Status Codes — Modern API Architecture: REST, GraphQL & gRPC
- Headers And Content Negotiation — Modern API Architecture: REST, GraphQL & gRPC
- API Gateways And Proxies — Modern API Architecture: REST, GraphQL & gRPC
- The ASP.NET Core Middleware Pipeline — Modern .NET Core, C# & Enterprise Microservices
- Server-Sent Events: Streaming Updates & Recovery — Production Full-Stack Engineering
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- What HTTPS Adds, And What It Does Not — Linux Fundamentals & Systems Administration
- Forward And Reverse Proxies — Linux Fundamentals & Systems Administration
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture