HTTP connection limit + cookie insert from BigIP

This is an old thread, but lines up with other ones that seem to want to limit the number of sessions. The code seems to be looking at the number of connections and limiting that to a threshold. The problem is that many client browsers will generate multiple requests from different source ports and the application session will continue through a series of transactions, each of which will generate (and drop) connections with the server. To me the logic may redirect a user who is in the middle of an active server session if they happen to send a transaction at at time that the overall connection limit is exceeded.