add the x-forwarded-for header to traffic from your cloud load balancer.
John Wojcik
shared this idea
Hi All,
X-Forwarded-For headers are now injected into all HTTP requests for existing and newly created HTTP load balancers.
Josh
5 comments
-
Brian Shensky
commented
I second Chris M's comment - I need the originating IP passed through the load balancers to my cluster nodes. X-Forwarded-For and HTTP_X_CLUSTER_CLIENT_IP are NOT AVAILABLE VIA HTTPS! Levi @ Rackspace explained that their load balancers can only provide IFF the HTTPS connection is terminated at the load balancer. But the Rackspace docs clearly outline that HTTPS termination at the load balancer is in conflict with many privacy-based issues (credit card, HIPAA, etc). We need the users IP address AS WELL AS running HTTPS through to the cluster nodes!
-
acgann
commented
Dates, guys, dates...how are we supposed to know if something is stable / new / whatever if you don't put dates on the posts?!
-
Brad Inscoe
commented
+3 votes. This should is a very high priority feature for those of us that have SaS applications to be able to track events and their originating IP
-
Chris M commented
@jonny yes but it looks like this is only available for HTTP traffic. HTTP_X_FORWARDED_FOR could be used for HTTPS traffic (I think some LBs take this approach), but currently neither HTTP_X_FORWARDED_FOR nor HTTP_X_CLUSTER_CLIENT_IP is sent for HTTPS requests, so there is no way to determine the client IP on HTTPS load balancers
-
Jonny Shaw
commented
If you want to use the clients IP address u can use HTTP_X_CLUSTER_CLIENT_IP
