Your case is definitely not unique --- we would also be very interested in such a patch since we are running Apache 3.20 in a production environment as a reverse proxy with several virtual hosts, all having some ProxyPass directives to the same web application (which selects a branding based on the virtual host name used, essentially). And we have of course experienced the same problem of figuring out how to get the proxied webapp to recognize which virtual host name is currently used. Your patch is just what we would need to get a clean and simple solution to this.
Morten - ---------------------------------------------- Morten Bj�rhus, TTYL http://www.ttyl.com ---------------------------------------------- ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Apache .Org Mod_Proxy" <[EMAIL PROTECTED]> Sent: Thursday, January 24, 2002 7:27 PM Subject: patch: proxy-preserve-host > In the current code you can't reverse proxy to virtual hosts or any other > host that relies on a host header because the original host header is > deleted and a new host header is created using the proxy's idea of the > hostname. This patch creates a config option called ProxyPreserveHost which > allows you to tell apache to send the original host header instead of a new > one. > > Might anyone else be interested in this patch or is my case unique? > > It's really only useful during reverse proxying and not during regular > proxying so do you think that I should only enable the option if > ProxyRequests is not on? Or, better yet, should I detect if a certain > proxied request is reverse and not regular and only then preserve the > original host header? If so, then what's a good way to distinguish the > reverse from the regular proxied request? > > Additionally, I'll may be using this in a production environment so I'd > really appreciate knowing of any potential bugs that anyone might see. > Anyone have any other suggestions? > > - Gabriel Russell > > (See attached file: proxy-preserve-host.diff)
