If using arrowpoint cookie balancing to stick a client to a particular service during the session what happens if the client doesn't send the cookie? There's an application that does this when looking at a trace on the client side:
1) start TCP connection
2) send HTTP POST, expect HTTP 100 CONTINUE
3) CSS responds with HTTP 100 and SET COOKIE in the response
4) Client then continues but does not include cookie or even HTTP commands, just continues the post as a continuation of TCP segments.
This is not a browser based application but a specialized app used for transfering data. Of course the "problem" is the CSS is sending this content to different services.
This is for a particular TCP conversation, the client opens other TCP connections with the same behavior. Arrowpoint cookie was choosen because of the need for stickiness to complete the process. The content rule is straight forward - uri "/*", advance balance arropoint-cookie, appropriate services and protocol, etc.