Same URI Different Pool

I have been load balancing my requests based on the URI of the request. If the request is /A then goto pool A. However, I have a new request comming in called /osso_login_success (its an oracle thing). The request needs to go to either Pool 1 or Pool 2 based on the orginial call. Here is the flow.

 

 

User types in a request for a J2EE application. That request is directed to the J2EE pool. The server at that pool issues a 302 and redirects the request to another VIP so that it can be authenicated. When the request comes back, it should go to the J2EE pool to continue.

 

 

Now, the user wants to run a Oracle Forms application. That request goes to the FORMS pool. Once authenicated, it should go back to Forms pool to continue.

 

 

The problem is that once authenicated the URI is the same. I just can't figure out which pool to send the request back to.

 

 

I did set a persistance cookie. Instead of my usual if "URI" goto pool, could I do something like If URI then goto the persistance pool/server? Could I attach a string to the request and do something like If URI then if string is "J2EE goto j2ee pool?

 

 

What is the best approach to this problem