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

peter_cuenco_73's avatar
peter_cuenco_73
Icon for Nimbostratus rankNimbostratus
Jun 21, 2006

Persistence within iRules

Hi,

 

I'm a newbie with iRules, but have a need for the following scenario -

 

 

VIP (my.company.com) is defined with cookie persistence. The VIP uses an iRule that basically reads -

 

 

when HTTP_REQUEST {

 

if { [string toupper [HTTP::uri]] contains "/Pool1/" } {

 

pool Resources

 

} elseif { [string toupper [HTTP::uri]] contains "/RESOURCES/" } {

 

pool Resources

 

} else {

 

pool my.company.com

 

}

 

}

 

 

I need to have sessions destined for /Pool1/ or /Resources/ be sticky, ie, once a user gets to server1 in the pool for /Resources/, the same server1 needs to be used for /Pool1/ requests as well.

 

 

Is there a way to this?

 

 

Thanks!

11 Replies

  • Thanks, Aaron. I did get this response from support:

     

     

     

    As for oneconnect and cookie persistence, the ENE I spoke to said that with oneconnect we will view all cookies within a single packet. If it was a pipelined packet from a proxy server, it would have more than one request from more than one client within a single packet. If you do not have oneconnect, we would just look at the first cookie in the packet even though there might be more than one cookie.

     

     

    Without oneconnect, we will see persist based on the session cookie. It is not required to have oneconnect turned on for cookie persistence.