You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many load balancers / proxies automatically set the X-Forwarded-For HTTP request header to indicate the original IP of the client. The Application Insights SDK for .NET uses this header when present to fill in the client IP, but the Java SDK does not. For more details, see http://apmtips.com/blog/2016/07/05/client-ip-address/
The fix would be to copy what the .NET SDK does: handle X-Forwarded-For automatically by default, while still allowing the ability to specify an alternative HTTP header name for the IP.
The text was updated successfully, but these errors were encountered:
Many load balancers / proxies automatically set the
X-Forwarded-For
HTTP request header to indicate the original IP of the client. The Application Insights SDK for .NET uses this header when present to fill in the client IP, but the Java SDK does not. For more details, see http://apmtips.com/blog/2016/07/05/client-ip-address/The fix would be to copy what the .NET SDK does: handle
X-Forwarded-For
automatically by default, while still allowing the ability to specify an alternative HTTP header name for the IP.The text was updated successfully, but these errors were encountered: