Hello,
Am new to pound and very impressed with it-  looking forward to replacing
my elderly apache reverse-proxy setup with pound.!

One small problem I have is that my back-end weblogic servers expect to see
the client's real IP address in a different request header than
X-Forwarded-For.
They expect it to be in a proprietary header WL-Proxy-Client-IP ( which is
currently added by a weblogic apache module ).

Does pound have any mechanism to create such a header (ideally on a
per-Service basis) , and populate it with the client IP?

Apologies if this is a FAQ.
many thanks
Robin
London, UK

Update - I just found an old post from 2005 in the mailing list archive
which looks outlines a way to do this by modifying http.c :  would this
still be the recommended way to add a custom header ?

just add a line to http.c such as:

         /* put additional client IP header */
         BIO_printf(be, "X-Forwarded-For: %s\r\n", inet_ntoa(from_host));
+        BIO_printf(be, "REAL_REMOTE_ADDR: %s\r\n", inet_ntoa(from_host));




On 11 November 2011 16:42, Robin Sinclair <rsinklair(at)gmail.com> wrote:
[...]

On 11/11/2011 11:53 AM, Robin Sinclair wrote:[...]

To my knowledge, yes, a custom patch is still required.  It probably 
wouldn't be too hard to add a config option for this particular case. 
Give it a try and talk to Robert and see if there's any interest in 
having it merged.

Regards,[...]