Affinity cookie persistence between pools in application gateway
Argument is: Application gateway cookie persistence for different backend pool
I have already rise an SR for this issue.
If you have a configuration like:
domain/app1 forward to pool1 (server1, server2)
domain/app2 forward to pool2 (server3,server4)
A page that call resources in /app1 e /app2 everytime a different pool is hit from the same browser session a new affinity cookie is generated.
There is no persistence of affinity cookie between calls on different pools.
The affinity cookie should take care about server in different pool for session persistence. So if i have affinity cookie X this should be use to select always server1 in pool1 and always server3 in pool2, doesn't matter if url jumps from /app1 to /app2 ands viceversa.
Ryan Adler commented
We got bit by this today - why is this not handled correctly? I would even go so far as to say it should not be allowed to assign two different rules with two different backend pools the same HTTPSettings if that setting has affinity enabled.