Brian_Kenworthy
Nov 04, 2009Nimbostratus
Persistence Across pools via iRule
Hi all,
We are experiencing an issue which I need some expert feedback to see if we are doing this properly with out iRule....
We have a virtual server with an iRule applied that is inspecting the URI to redirect traffic to one of three different pools, here is the rule:
when HTTP_REQUEST {
switch -glob [string tolower [HTTP::uri]] {
"/vmsxml/order.asp*" -
"/vmsxml/status.asp*" -
"/_xml/ors/status_mismo21.asp*" -
"/_xml/ors/status.asp*" -
"/_xml/ors/rels_status_mismo21.asp*" {
pool uat.domain.com_B2B_HTTPS
}
"/batchprocessing*" {
pool uat.domain.com_BatchPro_HTTPS
}
default {
pool uat.domain.com_HTTPS
}
}
}
Users have to first log into the website behind the pool uat.domain.com_HTTPS which is using an HTTP cookie insert profile. From that website, they access a link which directs them over to the uat.domain.com_BatchPro_HTTPS pool with a very simple upload page in which the user uploads a file. While waiting for a stored procedure to return from the data import, the user is returned what appears to be a timeout after 10 minutes.
I am wondering if this is due to persistence not being set on the uat.domain.com_BatchPro_HTTPS pool? Is it possible that the browser is checking the cookie and redirecting back to the web server in the uat.domain.com_HTTPS pool? I came across some posts about universal persistence so I am wondering that that is what we should be looking at?
Thanks in advance for any help.
-Brian