I have a problem to configure user identification via the X-Forwarded-For.
I configured it in the RUM Console, at the overall AMD level and in the software service.
Despite this, it is always the address of the load balancer that is raised in the CAS, and not the user address.
I attach a capture that shows the field X-Forwarded-For.
Someone would have any idea?
Check the following posts and I hope this will resolve your problem.
the HTTP Stream shows :
GET /astre HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:53.0) Gecko/20100101 Firefox/53.0
Accept-Encoding: gzip, deflate, br
Did you try to "mask" the spaces? I had a customer project some time ago where the Header with the client-ip was named "REAL-CLIENT-IP" and we needed to put in this kind of regex to extract the IP-Adress:
Good catch, looks like spaces are before and after IP address. Try to with the option of extracting it from header by the regular expression like
or maybe something like
Looking at the provided trace - there is only traffic from the client to the server (172.16.0.231 -> 10.110.11.50). There needs to be bi-directional traffic for the decode to work. I don't think the http parser will be invoked to parse the traffic if there is only one direction of traffic.
How did you capture this traffic and what filter did you use? Is the bi-directional traffic reaching the AMD? I think once the server responses are there the x-forwarded-for will be used to retrieve the client's real address.