Reverse proxy
A reverse proxy accepts requests in front of an application and forwards them. Routing, connection boundaries and forwarded information need clear rules.
What is a reverse proxy?
A reverse proxy sits in front of one or more application services. It accepts client requests, forwards them to the intended service and returns that service's response. The NGINX documentation shows this flow and the handling of forwarded headers. Depending on configuration, the proxy can perform further tasks.
Example: setting up shared portal access
In a fictional design, the proxy is the public access point. It distributes different requests to the intended internal services. The team defines which names and paths lead where and which information the application should receive about the original request.
Information freely set by the client must not be treated as trusted proxy information without checking. It must also be clear whether a protected connection ends at the proxy and how the next connection is protected.
The proxy alone does not replace application project permissions. Correct forwarding and a request permitted by business rules must be checked separately.
Sources
Related terms
- Hypertext Transfer ProtocolHTTP governs requests and responses between client and server. The method, status and content must fit the agreed application behaviour.
- Load balancerA load balancer distributes connections or requests across several destinations. Distribution rules, state handling and failure checks determine its behaviour.
- Transport Layer SecurityTLS protects data in transit between its endpoints. Application permissions, stored data and further connections need their own measures.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support