Forum Discussion
Chad_Roberts_21
Nimbostratus
NimbostratusRe-route on timeout
I found previous threads that discussed reacting to timeouts in various ways, but all the ones I found were from early 2005 and determined that it could not yet be done. With much time having passed, new versions of 9.x being released, and creative new ways to approach iRules, does anyone know a way to accomplish this?
I am attempting to write a rule that will check to ensure that a user's request was fully answered. We have a complex architecture here that could produce a number of different ways to delay communication to the point of timeout, so I want to either forward to an alternate pool or use HTTP::respond to throw in a response immediately.
Can this be done?
Chad_Roberts_21That's a good question, and I suppose that's going to take some thought to define, but for the sake of having some kind of protection, let's just say for a timeout waiting for response from the server in question. We have circumstances here where a port will be open and pass the initial "GET /" but fail to respond when certain paths are requested, for example. Is it possible to monitor whether a user's request goes unanswered and then retry with another pool or something?- This will likely be solvable in the future when we add timer events that you could have trigger additional actions, like disconnect the server and re-attach to a new one or provide a response to the client.
