On Mon, Jul 22, 2002 at 08:34:08AM +1000, Jie Gao wrote: > On Sat, 20 Jul 2002, Ask Bjoern Hansen wrote: > > > As you may know then the proxy module in httpd 2.0 incorporates the > > X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Server > > functionality of mod_proxy_add_forward.c. > > What are the differences between them?
I believe there is a difference in what headers was decided on to send in mod_proxy. mod_proxy_add_forward.c: X-Forwarded-For X-Host X-Server-Hostname mod_proxy: X-Forwarded-For X-Forwarded-Host X-Forwarded-Server > I have: > > ProxyPass /my-bin/ http://127.0.0.1:8081/my-bin/ > ProxyPassReverse /my-bin/ http://127.0.0.1:8081/my-bin/ > > and I still see > > 127.0.0.1 - - [22/Jul/2002:08:32:53 +1000] "GET /my-bin .... That's what's supposed to happen. On the backend you have the headers you can use to determine the original client. I've created a module (both 1.3 and 2.0) to take advantage of the headers called mod_rpaf [1] (reverse proxy add forward) in the backend. 1: http://stderr.net/apache/rpaf/ -- Thomas Eibner <http://thomas.eibner.dk/> DnsZone <http://dnszone.org/> mod_pointer <http://stderr.net/mod_pointer> <http://photos.eibner.dk/> !(C)<http://copywrong.dk/> <http://apachegallery.dk/> Putting the HEST in .COM <http://www.hestdesign.com/>
