[
https://issues.apache.org/jira/browse/KNOX-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003555#comment-16003555
]
Larry McCay commented on KNOX-390:
----------------------------------
Going to extend this capability to recognize the existence of HTTP headers that
have been set by upstream proxy servers in front of Knox. Since, the various
reverse proxies available on the market or in opensource may use different
header names and/or be configured to use a particular name for your
environment, I am going to make the header name to interrogate configurable.
The default will be X-Forwarded-For.
Even with this mechanism, it is still likely that the ip address will not be
the actual client ip but this is the best we can do.
> Include client IP and HTTP verb in audit log
> --------------------------------------------
>
> Key: KNOX-390
> URL: https://issues.apache.org/jira/browse/KNOX-390
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.4.0
> Reporter: Kevin Minder
> Assignee: Larry McCay
> Fix For: 0.13.0
>
> Attachments: KNOX-390-002.patch, KNOX-390.1.patch
>
>
> The audit log should include the client's IP address as well as the incoming
> and outgoing HTTP verb.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
