Support for extracting outermost client from X-Forwarded-For #11
Conversation
This commit adds naïve support for extracting the real client from the X-Forwarded-For header as set by various cache and proxy services. This implementation does not enforce or require that upstream has set X-Forwarded-For correctly, but merely splits on `, ` and is able to interpolate %x in the logging format to the outermost clients ip.
|
By the way, |
|
As the documentation says this plugin mimics Apache mod_log_config format strings. |
|
Ok. Thats fine. Just to clarify; the patch is meant to provide convenience so that information is made more easily available about the real client accessing the application. Instead of having to do extraction of that data through a separate step when processing log-data, or while looking at / grepping through the data manually. |
These two commits add support for using
%xin the log format to extract the outermost client as set in theX-Forwarded-Forheader. This is useful in situations where you have multiple proxy-layers and perhaps already log the header with%{X-Forwarded-For}ibut would like to have the convenience of logging the client ip in a separate field, for example instead of using%h.I have tried to follow conventions already present in the code of this module, but feel free to point out any discrepancies or things that would need correcting for this pull-request to be accepted.