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

Brad Allison <[email protected]> Wed, 24 Jan 2018 15:34:42 -0500
Newsgroups gmane.comp.web.pound.general
Message-ID <[email protected]>
--001a114b310ed6bc8905638b97ab
Content-Type: text/plain; charset="UTF-8"

Anyone know?

On Fri, Dec 15, 2017 at 11:39 AM, Brad Allison <[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
>

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

<div dir=3D"ltr">Anyone know?</div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Fri, Dec 15, 2017 at 11:39 AM, Brad Allison <span dir=
=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">br=
[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div class=3D"HOEnZb"><div class=3D"h5"><div dir=3D"ltr">I have apache/mo=
dsecurity running locally on the same server as my pound server.=C2=A0 It t=
akes the connections and runs the WAF rules, then hands them to pound.<div>=
<br></div><div>Problem is, pound is logging all connections as 127.0.0.1 be=
cause they are coming locally from apache.<br><br>Since pound used syslog t=
o log, how do I add X-ForwardFor to the log format for pound so I can see t=
he actual IP of the source of the request in the pound logs.</div><div><br>=
</div><div>-b</div></div>
</div></div></blockquote></div><br></div>

--001a114b310ed6bc8905638b97ab--

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