Thanks to Gerald Richter, Vivek Khera, and Ilya Obshadko for suggesting
the solution to the X-Forwarded-For problem I was having.
After a little bit of experimentation, it would appear that
mod_proxy_add_forward module needs to appear before mod_proxy (and
therefore be lower down Apache's execution order) in the Apache
configuration. Using the ClearModuleList and AddModule directives to
specify the required module order solved the problem.
In hindsight, this makes a great deal of sense, especially since
mod_proxy_add_forward first checks if it's dealing with a proxy request,
and this can only be true if mod_proxy has had a chance to execute.
Thanks again!
--
// 2 Ewan Edwards {e^2} -=-=- Web Developer for CSP Internet
// ----------------------------------------------------------------
\\/ / mailto:[EMAIL PROTECTED] 4252 Commerce Circle, Victoria, B.C.,
\\/ http://www.csp.net/ Canada (250) 953-2680, Fax 953-2659
What is worth doing is worth the trouble of asking somebody to do.
