X-Forwarded-For HTTP header being overridden by dash enterprise

I have a dash app which i am having to proxy through nginx, what i would like to do is make use of the X-Forwarded-For header nginx sets per reverse proxy.

The issue i am experiencing is that the value of X-Forwarded-For is the IP address of a container within the dash environment. 'HTTP_X_FORWARDED_FOR': '' and does not contain the forwarded-for ip addresses i would expect to see.

This leads me to think dash enterprise is overriding or not correctly setting a forwarded-for header. How do i get access to the downstream forwarded-for IP addresses.

It appears to be other headers are also overwritten, this includes 'HTTP_X_FORWARDED_PROTO': 'http',.

I have set other custom headers in the down stream and they are present in my dash apps request context. So this is leading me to think its a dash enterprise stripping the http headers.