Ok, here goes:
I am using http get method for service availability.
Scenario:
I connect to the content rule on port 80.
I then transition all the services to down by renaming my index.asp file (the file used for my http gets). I then verify that my session is still established by doing a netstat -an. I then make another http get request by clicking a link on my web page. Now, since all the services for that content rule are down, I would expect to get some kind of http 400 (404) error. Instead, I continue to be directed to a service within my content rule. I don't get this. All my services for that VIP are in a down or suspended state, and the content rule should not allow my get requests to be serviced by a service defined in my content rule when all services are down.
I have tried all of the options with persistence reset-remap/redirect, and bypass persistence disabled.
I am not using sitcky, and my webNS version is 5.02 (3).
Why are sessions that have been established prior to the services transitioning to down still being serviced? Can someone PLEASE help me, as the opinions from TAC have contradicted themselves (i.e. the css will not redirect existing sessions) while confguration examples on Cisco's site say that connections will be seamlessly redirected.
In any case, I am frustrated at the lack of clear answers I have been getting.
Thanks!
