vCloud edge gateway loadbalancer for HTTPS traffic not propagating original source IP

Hello,

I'm trying to use vCloud edge gateway load balancer in front of a pool of nginx server performing SSL termination. However, from what I see in the nginx http/https access logs, the source ip is always the external IP of the

The VCD load balancer is configured with two services enabled: http and https, with respectively none and sessionId persistence method (as to preserve https resumed handshakes).

Here is the nginx configuration made to verify this

log_format main '$remote_addr - $remote_user [$time_local] "$request" '

'$status $body_bytes_sent "$http_referer" '

'"$http_user_agent" "$http_x_forwarded_for"';

For HTTPS traffic I see $remote_addr always being the IP of egde gateway on the organization network it is connected to, instead of being the original ip of the http client.

For HTTP traffic, I see $remote_addr always being the IP of egde gateway on the organization network it is connected to, and the X-Forwarded-For header is not completed with the IP of the edgegateway.

Is it a known limitation ? I could not find anything mentionned into  VMware vCloud Networking and Security 5.1.4 Release Notes

Versions used: vCloud Director (version 5.1.3) and vCloud Networking and Security (Version 5.1.4).

Thanks in advance,

Guillaume.