GELF HTTP X-Forwarded-For headers not honored

[ed-graylog]

What?

As a Graylog user utilizing the GELF HTTP input I expect the X-Forwarded-For headers to be honored when using a load balancer.

Why?

Currently when using any load balancer when explicitly stating the headers in Graylog they are not honored, as a result the IP/client address shows as coming from the load balancer and not the actual client.

See HS-565348230 for details.

[danotorrey]

Related: https://github.com/Graylog2/graylog2-server/issues/2413

[emrecio]

Has graylog been able to read RFC 7239 Forwarded headers spec yet? It's been out since ~2014 and Jetty is requiring this format... I am getting some pushback from our WAF folks because it would make decoding this in graylog difficult. I am not too familiar with the greylog implementation here.