Reverse proxies

A reverse-proxy application publishes one or more domains and forwards requests to HTTP or HTTPS upstreams. Use it for services that run elsewhere or for applications whose process lifecycle ServerChirp should not own.

Upstreams and routes

An upstream can use an IPv4 address, IPv6 address, or DNS name. Define up to 20 path-based routes and choose a fallback route for unmatched requests.

Each route can:

• Preserve or strip its matched path prefix.
• Preserve the original Host header or replace it.
• Enable WebSocket upgrades.
• Disable proxy buffering for streaming or server-sent events.
• Set connect, send, and read timeouts.
• Verify upstream TLS with a separate TLS server name.

Example

Domains and SSL

The public side uses the same domain, certificate, redirect, HSTS, and Nginx validation flow as a normal web application. Upstream TLS is configured separately from the certificate presented to visitors.

Uploads and streaming

Set the proxy's client upload-size limit to match the application. Disable buffering only for routes that need live streaming; broad buffering changes can increase memory use and reduce Nginx's ability to protect a slow upstream.