Comment #2 on issue 3003 by matthew....@gmail.com: Impossible to use
nginx-apache proxy when running reviewboard
http://code.google.com/p/reviewboard/issues/detail?id=3003
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?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.
