In a location context (do not believe I can use a directory as it is being proxied), I thought about that. I felt it was better to mirror the current ProxyPass configuration item for consistencies sake.
For example : ProxyPass /cgi-bin http://otherserver.com/cgi-bin is the current standard as opposed to <Location> /cgi-bin http://otherserver.com/cgi-bin </Location> So I just went with that style. > On Wed, Feb 23, 2011 at 7:12 PM, Jeffrey E Burgoyne <[email protected]> > wrote: >> I am doing some work with a large organization that has recently >> acquired >> two products that work properly through a reverse proxy system only when >> ProxyPreserveHost is set to on. >> >> The organization had issue as they are mandated to have only a single >> hostname as a point of entry for their web applications. They have many >> technologies in the backend for web applications, and use different >> context roots and proxies to manage a reverse proxy system to a few >> dozen >> back end boxes. >> >> As ProxyPreserveHost can only work on a virtual host level, I could not >> properly configure the web server to deal both with these applications >> and >> the current configuration at the same time (as it broke all the back end >> technologies). >> >> >> To solve this I made changes to mod_proxy specifically for them, but if >> there is interest I can provide the code changes back to apache to >> incorporate into the next release. >> >> Effectively, I added a new command that mirrors the idea of separate >> ProxyPass lines, example : >> >> ProxyPreserveHostURL /idm/ >> ProxyPreserveHostURL /SepApp/ >> >> >> This effectively does the same as PreserveProxyHost, but only when the >> URL's start off with the supplied parameter. >> >> > > Would it not be simpler to just expand ProxyPreserveHost to be valid > in a directory context? > > Cheers > > Tom > -- Jeffrey Burgoyne Chief Technology Officer KCSI Keenuh Consulting Services Inc www.keenuh.com [email protected]
