Forum Discussion
Hi, I think you'll need to incorporate some form of automation in conjunction with your continuous deployments. Deploy a new version of the pool (with new monitor) using iControl, as each new version is deployed, and use the same process to remove pools no longer in use. It's the only way I can think of to get the flexibility you need.
A request with an invalid cookie value will (with the iRule above), cause a TCL error (and subsequent RST) should the pool requested not exist. You can make this more elegant by using the 'catch' command to allow you to return a valid HTTP response to the user rather than a RST should the pool "pl_server_[string tolower [HTTP::cookie value "AV"]]" not exist.
I don't see any risk of DoS with the strategy above that doesn't exist with any virtual servers with cookie persistence configured.