Serve an app under a sub-path with an nginx reverse proxy (strip the prefix) — by Jens Bradler on Server Fault

advancedforumCC BY-SA (Stack Exchange; version depends on post date)

To publish a backend at /foo/ without redirecting the browser, use a transparent rewrite inside the location block (rewrite ... break) and then proxy_pass. A 301/302 redirect would send visitors to an internal address they can't reach. The answer also suggests testing with curl -i.

Quick steps

location /foo { rewrite /foo/(.*) /$1 break; proxy_pass http://backend; proxy_redirect off; proxy_set_header Host $host; }

Paraphrased from the source. Menus can differ by version, so check the original for full details.

Read the full thread on serverfault.com

Source: Serve an app under a sub-path with an nginx reverse proxy (strip the prefix) by Jens Bradler on Server Fault. Licence: CC BY-SA (Stack Exchange; version depends on post date).

Source reviewed: 2026-11-02
Link checked: Not yet
Tested hands-on: Not by Oddbyte.Me

nginxreverse proxyrewriteproxy_pass

More in Community Answers (Stack Exchange)

Load balancer vs reverse proxy: what's the difference? — by icky3000 on Server Fault

beginnerforum

A plain-English explanation: a load balancer spreads requests across several servers, while a reverse proxy is a broader tool that can load-balance and also cache, terminate SSL, compress and filter traffic. Often one product does both jobs.

Reach several home devices from outside through one IP using subdomains — by Daniel on Super User

intermediateforum

With one public IP and a domain, run a single nginx reverse proxy that sends device1.example.com, device2.example.com and so on to different internal servers by name. Only that one proxy needs ports forwarded. Anything exposed this way should be secured (HTTPS, authentication) or kept behind a VPN instead.

Why put nginx in front of your app server? — by blueben on Server Fault

intermediateforum

Explains the benefits of a reverse proxy in front of an application server, focusing on slow clients: nginx buffers slow connections so the limited app workers stay free. It also covers SSL handling and absorbing traffic spikes.