You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Saksham Srivastava (JIRA)" <ji...@apache.org> on 2014/11/19 11:53:33 UTC
[jira] [Resolved] (CLOUDSTACK-7941) CloudStack should log IP
address of actual client even if a ReverseProxy is there
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saksham Srivastava resolved CLOUDSTACK-7941.
--------------------------------------------
Resolution: Fixed
> 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)