One HTTPS virtual to several HTTPS pools

Deb, I just wanted to clarify something you've said several times now.Without OneConnect enabled, only the first request in a Keep-Alive connection is parsed for persistence data, so if multiple requests are sent on the same clientside Keep-Alive connection, LTM will persist them all to the same destination as the first.This is not entirely accurate. In fact, the BIG-IP parses all requests as long as the HTTP profile is on the virtual (and not disabled). However, the serverside connection is maintained unless either OneConnect is enabled or a new pool is picked. So, in this case, I would have expected it to change pool assuming the uri changed to one of the other values. This is often confused with the issue that the default pool is not automatically re-selected when there is no "else" clause.

 

 

Here are some similar posts from a long time ago explaining the details of enabling/disabling OneConnect and pool selection:

 

 

(Click here) http://devcentral.f5.com/Default.aspx?tabid=28&view=topic&forumid=5&postid=1636

 

(Click here) http://devcentral.f5.com/Default.aspx?tabid=28&view=topic&forumid=5&postid=5336

 

(Click here) http://devcentral.f5.com/Default.aspx?tabid=28&view=topic&forumid=5&postid=6751