1

I need to enable a web application to be served from a non-root path (i.e. http://example.com/wiki/ instead of http://example.com/). The application is behind a reverse proxy (nginx). I realized there are at least two approaches to this:

  1. Make the app aware of the path prefix and use it to construct all URLs (Location headers in 3xx redirects, links within HTML docs and addresses in Ajax calls).

  2. Strip the prefix from the request in the reverse proxy (/wiki/index.html becomes /index.html), pass such request to the app, use relative URLs in all HTML docs and Ajax calls (src="./static/foo.jpg", POST "./create-user". Configure the reverse proxy to rewrite Location headers returned in redirects. ('proxy_redirect' nginx directive).

Which approach is better and why?

Oded
  • 489,969
  • 99
  • 883
  • 1,009
Jan Wrobel
  • 6,969
  • 3
  • 37
  • 53
  • What language and platform are you on? – Oded Oct 13 '12 at 18:49
  • This particular application is in Rails, but I don't think the recommended approach should differ for different frameworks. – Jan Wrobel Oct 13 '12 at 18:52
  • Well, some frameworks have the solution built in. http://stackoverflow.com/questions/3077558/use-of-tilde-in-asp-net-path – Oded Oct 13 '12 at 18:55

0 Answers0