Pound will transmit X-Forwarded-For to the backends, and you can use Mod Extract Forwarded or similar to parse and use them in other software packages. It doesn’t look for a header from the front-end side and adjust its own behavior.
------ Joe CONFIDENTIALITY STATEMENT The documents and communication included in this email transmission may contain confidential information. All information is intended only for the use of the above named recipient(s). If you are not the named recipient, you are NOT authorized to read, disclose, copy, distribute, or take any action on the information and any action other than immediate delivery to the named recipient is strictly prohibited. If you have received this email in error, do NOT read the information and please immediately notify sender by telephone and email and immediately delete this email. If you are the named recipient, you are NOT authorized to reveal any of this information to any unauthorized person and are hereby instructed to delete this email when no longer needed. From: Matt Park <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, January 24, 2018 at 5:08 PM To: "[email protected]" <[email protected]> Subject: Re: [Pound Mailing List] apache/modsecurity in front of load balancer Aren't you supposed to use mod_headers or similar to add x-forwarded-for from the apache side? Pound should pick it up right? On Jan 24, 2018 3:39 PM, "Brad Allison" <mailto:[email protected]> wrote: Anyone know? On Fri, Dec 15, 2017 at 11:39 AM, Brad Allison <mailto:[email protected]> wrote: I have apache/modsecurity running locally on the same server as my pound server. It takes the connections and runs the WAF rules, then hands them to pound. Problem is, pound is logging all connections as 127.0.0.1 because they are coming locally from apache. Since pound used syslog to log, how do I add X-ForwardFor to the log format for pound so I can see the actual IP of the source of the request in the pound logs. -b
