3003: Impossible to use nginx-apache proxy when running reviewboard

mech*****@gmai***** (Google Code) (Is this you? Claim this profile.)
June 11, 2013 
What version are you running?
1.7.7.1

What's the URL of the page containing the problem?
Any URL

What steps will reproduce the problem?
1. Create apache2 virtual host using provided master.
2. Create nginx virtual host which is proxy to the apache host 
3. Use proxy_pass directive to apache, like, proxy_pass         http://localhost:88;
4. Enable the host, open reviewboard, try to create the review

What is the expected output? 
Review is created successfully. All links are modified in accordance with proxypass directive

What do you see instead?
One can login to the system, but review can not be created -- the requests are generated properly, but system responses are all wrong -- you generate the path from the beginning -- <hostname in apache>:<port in apache>/path, so the proxy modifications are ignored completely.
Though the proper behaviour is to create path starting from document root only leaving the hostname non-modified. That's the responsibility of web-server, not web-application.

What operating system are you using? What browser?
Debian 6.0, MySQL 5.1, browser-independent issue.
david
#1 david 
You can configure the server name in the admin settings. In this case, the web application *does* need to know the hostname, because it also sends out emails with links and provides fully-qualified URLs in the web API, and we don't make a distinction internally between the three different places that we generate URLs.
  • +SetupIssue
#2 matthew*******@gmai***** (Google Code) (Is this you? Claim this profile.) 
I believe I am having a similar issue of not the same. I run three reviewboard instance on one server, and I would like to use a proxy with a central cname that proxy accordingly to the various reviewboard instances.

I created an app cname called r1, r2, and r3. Which works perfectly, but I want to have one central cname to control access to these.

An example:

cname reviews
proxypass /app1 http://r1
proxypassreverse /app1 http:/r1

proxypass /app2 http://r2
proxypassreverse /app2 http:/r2

The reviewboard instances all look great when access, but new reviews cannot be submitted as the request behind the scenes is r1 vs. reviews/app1.

To fix this, proxypreservehost on would usually be used, but this just then kills the request with a 502 error. I tried a few things like proxybadheader ignore or startbody to try to resolve, but with no success.

Anybody got any suggestions?
david
#3 david 
Assuming you never care to access the server at http://r1/, you could set the site root in settings_local.py. There's no way to have Review Board answer to both / and /app1/