[Pound Mailing List] apache/modsecurity in front of load balancer

--089e082d27142b40c0056063a43c
Content-Type: text/plain; charset="UTF-8"

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

--089e082d27142b40c0056063a43c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have apache/modsecurity running locally on the same serv=
er as my pound server.=C2=A0 It takes the connections and runs the WAF rule=
s, then hands them to pound.<div><br></div><div>Problem is, pound is loggin=
g all connections as 127.0.0.1 because they are coming locally from apache.=
<br><br>Since pound used syslog to log, how do I add X-ForwardFor to the lo=
g format for pound so I can see the actual IP of the source of the request =
in the pound logs.</div><div><br></div><div>-b</div></div>

--089e082d27142b40c0056063a43c--

--
To unsubscribe send an email with subject unsubscribe to [email protected]
Please contact [email protected] for questions.