[
https://issues.apache.org/jira/browse/CLOUDSTACK-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609882#comment-14609882
]
ASF GitHub Bot commented on CLOUDSTACK-8180:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/549#issuecomment-117583894
@remibergsma
I also think it's a bit annoying the commits with the same message, but we
have to inform the jira issue.
Next time I will add the jira issue number but not the whole description.
Instead of the description I will add the commit message... It will clarify
things.
Thanks for the review.
Cheers,
Wilder
> 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)
