intermediary
Any program or device between client and server that handles traffic, such as a proxy, cache, load balancer, gateway or firewall.
In more detail
Each one can terminate, rewrite or reset connections, so a failure may belong to it rather than to either endpoint. HTTP intermediaries act on the meaning of standard methods, statuses and headers, so a wrong status or method can cause bugs far from your code. Trace a request leg by leg to find where it stops.
Related terms
- reverse proxy — A server that receives requests on behalf of other servers and forwards them, returning their responses as if they were its own.
- HTTP cache — A store that keeps HTTP responses and reuses them for later requests, following the rules the server sends in Cache-Control.
- REST — An architectural style for networked software built on named resources, representations of their state, stateless requests and a uniform interface.
- 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.
- load balancing — Spreading requests or connections across several backend servers so no single one is overloaded and failed ones can be avoided.
- firewall — Software or a device that allows or blocks network traffic according to rules about direction, interface, protocol, port and source.
- connection reset — A failure where an endpoint or something in between abruptly ended a connection by sending a TCP reset (RST).
Taught in
- When Each Wins: REST, GraphQL, gRPC And SOAP — Modern API Architecture: REST, GraphQL & gRPC
- Refused, Timed Out, Reset: Reading A Failure — Linux Fundamentals & Systems Administration
- The Diagnostic Ladder: Is It Listening, Answering, Arriving — Linux Fundamentals & Systems Administration