Two different source nat for one VIP based on HTTP::URI

I'd be curious to know if this even selects the desired pool member if the initial request is for 'uri1', and a subsequent request is received that matches default. Assuming no pool member overlap between pools 'pool-www-11' and 'pool-www-22' I'd expect the actual result to be different than anticipated since, as you noted, the connection table entry has already been established.

This sounds like a situation where OneConnect or the LB::detach method would come into play. Those would allow detachment of the client from the server-side on a per-request basis and may enable the functionality you're looking for. Not posting as an answer since I can't give you a definitive "here's an example that will work" answer. Offering in case you hadn't considered those and I'll fill my knowledge from the next person that expertly answers this question. ;)