cloudstack-issues mailing list archives

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

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

ASF GitHub Bot commented on CLOUDSTACK-8180:
--------------------------------------------

Github user remibergsma commented on the pull request:

    https://github.com/apache/cloudstack/pull/549#issuecomment-117576939
  
    Thanks for fixing it, LGTM.
    Small comment: I see two commits with the same first line. Personally I'd prefer to see
from the first line what a commit implements.


> 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