Monitor Disables Node, persistent connections

Reselect is already set. Let me explain in more detail. The web node is relaying to an application node behind it. If the application node goes down, the web node displays an error page. I wrote a custom http monitor to check for the error message and disable the node if seen. The monitor is applied at the pool level and the action on service down is reselect. I load the homepage. Turn off the backend node. Wait for the Web node to be disabled then hard-refresh the page. At this point I would expect my request to get sent to one of the other web-nodes in the pool. Instead I see the error page. The LTM is redirecting me to a downed node. The node is still technically “up” it responds to tcp and serves http requests, but for all intents and purposes it’s dead, it is an ex webserver. Now, this behaviour may be understandable under some circumstances, but I certainly would not expect it to be the immutable default. Maybe if I could set apply the custom http monitor as the health monitor at the node level, maybe that would work. Maybe. But I can’t, because I can’t apply custom monitors as a “node specific monitor”.