Forum Discussion
hooleylist
Jan 08, 2010Cirrostratus
The wiki page for the persist command states that 'persist none' disables persistence for the rest of the TCP connection. So if you use the rule as it is, if a client makes a request for /app2, I think any subsequent request on the same connection would not get a persistence cookie. You could test this by adding logging to the iRule and using netcat (assuming it's an HTTP VIP) to open a TCP connection and then send a request for /app2 and then one for /app1. See if you get a persistence cookie in the response to /app1.
Here is an example from the LTM command line using netcat (nc):
$ nc 1.1.1.1 80
GET /app2 HTTP/1.0
Connection: keep-alive
GET /app1 HTTP/1.0
If it's working, in the response to the /app1 request you'll see a Set-Cookie header with the LTM persistence cookie.
Aaron