Pass X-Forwarded-For header from http requests into logs

[wf1nder]

We using http reverse proxy in front of some VM components. As a result, VM writing into logs proxy's address, instead of original client address, which sometimes makes it difficult to debug. Proxy passing original address in standard X-Forwarded-For header, but it looks like VM ignores it.

I suggest to support X-Forwarded-For header. If it presents in request, use its value in logs as client address, or write it as additional filed in logs.

[valyala]

Added X-Forwarded-For header in error messages in the following commits:

• Single-node version: 67a64c1
• Cluster version: 1e06740

These commits will be included in the next release.

[valyala]

The X-Forwarded-For header has been added to error logs starting from v1.39.2. Closing the feature request as done.

[valyala]

FYI, the X-Forwarded-For request header is shown at /api/v1/status/active_queries page starting from v1.39.3. This should simplify detecting clients that send heavy queries.