uie persistence

Again? (Click here). Could you try replying to your original posts if the topic is the same? It tends to waste time if you post the same question multiple times in different threads.

 

 

It sounds like you are wanting to insert your own session ID in response headers and content and then persist off of it if the client doesn't accept cookies. To do so, you'd need to parse the links in response headers (mainly the Location header for 30x responses) and all other responses with text payloads to insert a dynamically generated persistence token. On subsequent requests, you'd need to parse and remove the session token from the URI and persist based off of it.

 

 

It is technically possible to do this. I wrote a 1000 line iRule for a customer that implemented similar logic for encrypting/decrypting URI paths, but it's pretty complicated. I wouldn't recommend it for high traffic applications. Due to the complexity, I'd suggest any other solution first. And I don't think anyone here would be willing to write such a rule for you in their spare time.

 

 

For most applications, using cookie insert persistence with fall back source address persistence is enough. Does your user base really not accept cookies and have frequently changing source addresses?

 

 

Aaron