Specifying node kills cookie persistence

I started with that. Then I remembered this doc:

 

https://support.f5.com/kb/en-us/solutions/public/9000/800/sol9815.html

 

 

The issue in the doc isn't entirely relevant, but I thought to be safe, I'd try 'node'. If I recall correctly, won't 'node' use the default pool for the virtual server? In any event, both 'node' and 'pool' create the desired the effect: the initial HTTP request is directed to the desired node. It's just that pesky cookie won't get set. For what it's worth, the cookie IS inserted on the second GET. But by then the connection is usually re-load balanced, and I wind up on the wrong server. At one time I did try a fallback persistence profile using source IP for a few seconds -- enough for the second GET to hit the same server and then receive the cookie. This, I think, is rather kludgy, and should be unnecessary.