Auth_Status and Persist

Thanks for your inputs..APM requires more Cost Benefit Analysis in our env. I see some hope with uie persistence.

There are two pools in picture here PoolF and PoolK. Here is what i am currently happening VIP is configured with default pool as PoolF, cookie persistence enabled at vip and the following irule:

 when HTTP_REQUEST { 
   if { &91;HTTP::uri&93; contains "/nad" } { 
     pool PoolK 
    } 
  } 
 when HTTP_RESPONSE { 
 if { &91;HTTP::status&93; == 401 and &91;HTTP::cookie exists "PD-S-SESSION-ID-PROD2"&93;} { 
   HTTP::respond 302 Location "https://portal1.net/" "Set-Cookie" "F5-redirect-nad" 
   } 
 } 

User opens IE, types https://portal1.net/nad, PoolK is selected and cookie - PD-S-SESSION-ID-PROD2 sent to the client with 401, the HTTP_response sees it and redirect & replace uri from /nad to /.

At this point, i want the next or any future HTTP_REQUEST to persist on poolK from this client (because i am already authorized), but instead it is falling back to default PoolF and breaking my page because /nad is not in the uri?

Would persist add uie help along with cookie persistance or do i really need cookie persistence, will uie do the work? I have been looking into sol7392 but don't know yet how to utilize it to keep persist going for poolK.

_ _** **