On Thursday 24 September 2009, Alex Hermann wrote:
Scenario 2 breaks. It should enter branch route (or send out identical message by itself). From a usability standpoint, I would prefer that the behavior is identical for received 503 or internal 408. And as every failover creates a new branch, I think branch_route should be called everytime.
A quick workaround would be that on DNS based failover in case of a timeout, branch route is called again. I tried to find in the source the place where the decision is made whether or not to call branch route on DNS failover, but got lost.
A workaround seems to be to call t_on_branch() again in the branch_route itself.