Persist on unique uri argument

The problem with this iRule relates to the application process. As the persistence is required on the server that originated the response this rule works too late in the exchange between client and server. So, the client makes a first request to the server, this request is load balanced and there is no sessionId, the server then creates a session & sessionId for the client and sends the response. When the client makes the second request it is load balanced again and there is a sessionId so the connection will persist. However, the desired behaviour is not to load balance at this point but persist to the original web server, instead the request goes to a web server that has no knowledge of the session and the application breaks.