I've configured the following on ACE and CSS11500 respectively (left out the unimportant lines in the content-rule):
sticky http-cookie WPS6 sticky-nbp-wps6
cookie-insert browser expire
serverfarm sfarm-nbp-wps6 backup sfarm-nbp-wps6-sorry
arrowpoint-cookie name WPS6
Are there any major differences in how the ACE and the CSS handles cookie-based stickyness based on the above listed configurations? From what I've read, the CSS looks for the cookie-value at each GET and forwards traffic based on the value in the cookie. Only when the cookie expires, will traffic be subjected to the LB-algorithm again. But how exactly does the ACE handles this? Does is look for the cookie value at each GET and match it to the corresponding entry in the sticky-database? Or is this method only applied, when persistence-rebalance is configured? If I manually delete the cookie in the browser, will that in any way affect how the ACE handles the subsequent GET or will it simply reuse the sticky parameters applied at the first GET, until the cookie expires and is removed from the sticky-database?