For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

IheartF5_45022's avatar
IheartF5_45022
Icon for Nacreous rankNacreous
Mar 11, 2014

Look at this devcentral post. If you apply an http profile and cookie persist insert (with no oneconnect), the F5 will return a cookie (if none exists) and then persist the rest of that TCP connection to the same server. You can disable HTTP processing in HTTP_RESPONSE. Then the same cookie could be used in subsequent connections from the same browser to persist to the same server.

 

This might also solve your SSL issue.