Feng_Zhang_01_1
Apr 07, 2014Nimbostratus
client ip address unstable fails "source ip affinity"
We used source ip affinity in our F5 configuration, but it is not working as expected: A java client is getting load balanced to different instances within a minute. We noticed that client ip address changes after through x-forward-for address log. For example, a x-forward-for address example is "192.168.0.1, 172.16.0.1, 10.0.0.1", we can see for the failed client, the ip address we record using request.getHeader(X_FORWARDED_FOR_HEADER) some times return "192.168.0.1", sometimes return "10.0.0.1". Does anyone know the solution?