https redirection when node fails

This depends entirely on the application. Take for example an application that requires authentication and then sets a session cookie that maps to some memory-resident data on the server for that user. Every subsequent request sends the cookie, which maps to the session data, which lets the server know who the user is from one request to another. If the node fails over, there must be a mechanism in place for both nodes to "share" that (application) session data. For many platforms that's a central server or database that stores the session data instead of in resident memory. That's also something you wouldn't want to do with the BIG-IP (you could, but you generally wouldn't want to). So then it depends on the general complexity of the application and how it interacts with the user. If the application is simpler than the one described above, then other options may exist. If something like Access Policy Manager (APM) is handling the authentication, then that information would/could be persisted across nodes.