[
https://issues.apache.org/jira/browse/CLOUDSTACK-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610951#comment-14610951
]
ASF GitHub Bot commented on CLOUDSTACK-8180:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/549#issuecomment-117815608
Yep... Agree.
That's what I also suggested in my reply.
We are getting better... Next one will be perfect. :)
Thanks, guys!
Cheers,
Wilder
Sent from my iPhone
On 01 Jul 2015, at 22:17, Remi Bergsma
<[email protected]<mailto:[email protected]>> wrote:
I agree, ticket id is enough.
Sent from my iPhone
> On 01 Jul 2015, at 21:35, Miguel Ferreira
<[email protected]<mailto:[email protected]>> wrote:
>
> @wilderrodrigues @remibergsma @bhaisaab why not just put the the ticket
ID in the commit message?
> something like:
>
> CLOUDSTACK-8180: adding this
> CLOUDSTACK-8180: changing that
> —
> Reply to this email directly or view it on GitHub.
>
—
Reply to this email directly or view it on
GitHub<https://github.com/apache/cloudstack/pull/549#issuecomment-117813307>.
> 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)
