We discovered that existing sessions to our web application persist when our maintenance page is applied (by applying an iRule). The result is that they can still navigate and play content during a maintenance window.
I'm experimenting with the "action on service down" and cronjob activated commands to place the m-page, force offline pool members with one command, bring the pool members back up a minute later but leave the m-page up until completed. This sort of works but only for site navigation. The very next thing that a user will click will force them to the m-page which is fine but 9 times out of 10 a user will be watching video content which is coming from content servers, not the fe/be servers that are in maintenance.
Is there something I can do with an iRule that sends a command across existing connections that will tell the client's browser to terminate all their content connections as well?
Applying a m-page to our content servers wouldn't work since most people will be hitting Fastly servers.
Thinking outside the box a bit.
You could keep a global variable that says whether to continue to service content. Then add an iRUle that triggers events for data received. So you effectively get an event triggered for pretty much every packet. When you get the event,
When you trigger , check the variable to say whether the service is up or down. if it's down, drop the connection. If it's up, let the data through. you'd need some way to control the global that states of the service is up or down, but apart from that and some minor concerns about scalability, it should work...