Hi Viranga, Can I check if you've configured your backend web servers to use either the X-Forwarded-For or X-Client-IP header in your logging?
Normally you would need to do something like the following: http://www.loadbalancer.org/blog/iis-and-x-forwarded-for-header http://www.loadbalancer.org/blog/apache-and-x-forwarded-for-headers Otherwise without understanding your traffic flow it would appear correct, it's worth bearing in mind that XFF headers will usually contain the client IP followed by each successive proxy the connection went through so check it if contains multiple addresses. Aaron West Loadbalancer.org Limited +44 (0)330 380 1064 www.loadbalancer.org On 18 January 2017 at 03:38, Jayalath, Viranga <viranga.jayal...@pearson.com > wrote: > Hi Haproxy team , > > I have a question. I have a backed instance which attached to haproxy > instance. I have requirement to get client IP in my nodejs application > logs . But how ever im getting the haproxy IP. I refer all your x forwarder > options can use to get client ip but still im getting the haproxy server ip > in my logs. Can you advice any thing i can do . Below you i will mentioned > configuration changes i used. > > # add X-FORWARDED-FOR > option forwardfor > # add X-CLIENT-IP > http-request add-header X-CLIENT-IP %[src] > > > -- > Best Regards, > > Viranga Jayalath > DevOps and Application Engineering,Cloud Services Technology Operations > > Pearson Lanka (Pvt) Ltd. > Technology Operations > Orion City, Alnitak Building > No. 752, Dr. Danister De Silva Mawatha > Sri Lanka > > > *M* +94 (0) 714 672980 <+94%2071%20467%202980> > > Learn more at *pearson.com <http://pearson.com/>* > > *ALWAYS LEARNING* >
