cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8180) RouterVM does no longer provide X-ForwardedFor header with Loadbalancer
Date Fri, 10 Jul 2015 19:31:05 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622798#comment-14622798
] 

Rohit Yadav commented on CLOUDSTACK-8180:
-----------------------------------------

[~wilder.rodrigues] - does it need to be ported to 4.5?

> RouterVM does no longer provide X-ForwardedFor header with Loadbalancer
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8180
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8180
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.3.0, 4.4.2
>            Reporter: Steven Geerts
>            Assignee: Wilder Rodrigues
>              Labels: patch
>
> With the migration from Cloudstack 4.2.1 to 4.3.0 we lost the functionality that the
virtual loadbalancer (HaProxy) on a router VM added the "x-forwarded-for" header to the http(s)
traffic. 
> This header allows webservers to get the IP address from the originating host. 
> due to the absence of this header all webtraffic seems to originate from the (inside)
IP of the routerVM.  
> we confirmed this functionality to be absent/broken until CS 4.4.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message