Persistence issues when using two different Virtual servers for the same traffic

Question- are you performing SSL decryption/encryption on the Virtual Server A? In order to support cookie persistence on a HTTP/s virtual server in your architecture, the following pieces should be in place:

1. Virtual server A: clientside and serverside SSL profiles
2. Virtual server A: http profile (optional but recommended)
3. Virtual server B: clientside SSL profile (serverside SSL profile depends on whether the pool members have SSL enabled)
4. Virtual server B: http profile
5. Virtual server B: cookie persistence profile

With regards to the http profile for Virtual servers A and B, I would probably create a custom http profile where x-forwarded-for is enabled. That way, the "true" client IP address can be captured.