[
https://issues.apache.org/jira/browse/CLOUDSTACK-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610059#comment-14610059
]
ASF subversion and git services commented on CLOUDSTACK-8180:
-------------------------------------------------------------
Commit 23c664209a37419e20947c8e5af114bafa377ee5 in cloudstack's branch
refs/heads/master from [~wilder.rodrigues]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=23c6642 ]
CLOUDSTACK-8180 - RouterVM does no longer provide X-ForwardedFor header with
Loadbalancer
- Formatting code
Signed-off-by: wilderrodrigues <[email protected]>
CLOUDSTACK-8180 - RouterVM does no longer provide X-ForwardedFor header with
Loadbalancer
- Make sure the "option forwardfor" is always available by not removing it
- If keepalived is enabled, then set "no option forceclose"
Signed-off-by: wilderrodrigues <[email protected]>
This closes #549
> 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)
