Short version:

Does anybody have any experience, patches, advice for writing an alternate HTTP header to the access log rather than the raw client IP address?


Longer version:

Our hosting provider has recently modified the load balancing/proxy set up in front of our AOLserver 3.3.1ad13 servers. They're using linux boxen running IBM's Websphere Edge server for load balancing and its "content based routing". Now all requests appear to come from the IP address of the load balancing server rather than from the actual clients. The Edge server is configured to write the orginal client's IP address into a new HTTP header, "ext-ip".

I've identified where in nslog/nslog.c the necessary change would be made to write the value of this header rather than NsConnPeer(conn), but before I make the change, test, etc. I thought there might be an easier way that I'm overlooking.

Ideas?

thanks,

Doug
---

-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.

Doug Harris               (202) 473-3118              [EMAIL PROTECTED]

Reply via email to