It's funny that you posted this question. I actually have a somewhat related
problem that I was about to create a post for. First, here is my current
Apache config which works quite well except for the issue I mentioned that I
will detail after the config.:
Options ExecCGI FollowSymLinks
allow from all
ProxyPass / http://192.168.1.10:8080/ retry=0 connectiontimeout=5 timeout=30
ProxyPassReverse / http://192.168.1.10:8080/ retry=0
I am using the latest version of Apache 2.2 on Ubuntu 13.04 (Ubuntu has not
updated to Apache 2.4 yet; it's coming in 13.10). With this configuration,
I do not use the ProxyHTMLURLMap directive. Since you are using Fedora and
possibly a different version of Apache, it is possible that this config. may
not work exactly as well in your case, but it should be mostly the same.
Nearly everything works great with this setup--no broken links or references
or files that can't be found. It really is like connecting to the server
port directly. The one thing I've found that is not working is
authentication. I can use the login form and enter the correct password and
I see the cookie being written into the browser the public domain, but
MisterHouse never sees the user as authenticated...
At first, I was thinking that the reason why it wasn't working is because
the public side wasn't passing the cookie to the back end (MisterHouse
browser), so I tried dozens of configurations with the
ProxyPassReverseCookieDomain directive to rewrite the cookie domain from the
external domain name to the internal domain name (192.168.1.10, localhost,
etc. depending on your Reverse Proxy configuration). None of these
configurations helped... I turned on debugging for http in MisterHouse and
was able to confirm that the cookie is being passed into the header to
MisterHouse, so I am not sure why MisterHouse does not think the user is
I will keep trying to debug this issue, but if anyone has any ideas or can
post their working config., that would be great. One thing that I should
mention: I am using SSL from the user to the front end of the proxy and
non-SSL from the proxy to MisterHouse. Again, since the MisterHouse
webserver seems to be receiving the cookie, I do not think that this is the
problem, but I wanted to mention it just in case...
View this message in context: http://misterhouse.10964.n7.nabble.com/URL-Rewrite-tp18329p18331.html
Sent from the Misterhouse - User mailing list archive at Nabble.com.
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365