On Apr 25, 2013, at 11:32 AM, "Tom Evans" <tevans...@googlemail.com> wrote:
> It looks like you are rewriting it to it's current location. This > leads to a loop. > > Why are you using rewrite rules anyway? Because reverse proxy does not work > It seems like you want to > reverse proxy from an apache server with a public IP to a backend > webserver in your private LAN. Where do rewrite rules come in to this? > Why are you checking the host name in your rewrite rules, instead of > using vhosts? Why is this not your configuration: > > <VirtualHost *:443> As I stated in an earlier post, apache does not start when more than 1 ssl virtual host (complains about overlap) > ServerName apps.tld > ProxyPass / https://192.168.123.7/ > ProxyPassReverse / https://192.168.123.7/ > </VirtualHost> We have many different things that run on this server and apache handles them. When using "/" in your proxy config, everything stops working, email, other websites etc. > > I'm very confused by what you're trying to achieve. I covered this in my first email but will try to describe it again: server behind an apache server that we need users to get to using https://apps.domain.tld. The app resides at http://<server inside ip>/sub. We need apache to catch the https://apps.domain.tld request and send to https://another server/sub Thanks
