I built a proxy for Sentry events in order to create Sentry projects on demand and route traffic into the appropriate project based on metadata in the payload. We have a number of web properties with raven-js integration, so managing from a single place is desirable. This is working great, however, I noticed that we lose the client IP tracking - all of the events appear to originate from two IPs, which correspond to the public IP addresses of our proxy cluster.
I’ve double checked our proxy implementation, and its correctly setting the X-Forwarded-For header to include the original client IP. In fact, we’re using Golang’s httputil.ReverseProxy, so you can see the code here: https://golang.org/src/net/http/httputil/reverseproxy.go?s=3924:3999#L204
Does sentry.io honor X-Forwarded-For? If not, can it? Is there another alternative to get the client IP tracking working?