[
https://issues.apache.org/jira/browse/CLOUDSTACK-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283473#comment-14283473
]
ASF subversion and git services commented on CLOUDSTACK-7941:
-------------------------------------------------------------
Commit 6715c6ccfa68b53a3891f49ec98b568511c9cfb9 in cloudstack's branch
refs/heads/4.5 from [~saksham]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6715c6c ]
CLOUDSTACK-7941: CloudStack should log IP address of actual client even if a
ReverseProxy is there
(cherry picked from commit f0a4a639de231929bd63f673c4d6adc6bfb5ca80)
Signed-off-by: Rohit Yadav <[email protected]>
> CloudStack should log IP address of actual client even if a ReverseProxy is
> there
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7941
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7941
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0
> Reporter: Saksham Srivastava
> Assignee: Saksham Srivastava
> Fix For: 4.5.0
>
>
> In certain deployments there could be a reverse proxy in front of CloudStack.
> The event log "USER.LOGIN" is shown as 'user has logged in from IP Address
> x.x.x.x'. The IP address 'x.x.x.x' is the IP of the reverse proxy.
> In most deployments the reverse proxy/LB will add a HTTP
> header(X-Forwarded-For, HTTP_CLIENT_IP, HTTP_X_FORWARDED_FOR, Remote_Addr) to
> the request.
> CloudStack should try to get the correct client IP using these headers.
> This support must be added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
