5 Aug
2011
5 Aug
'11
5:52 p.m.
On Friday 05 August 2011, Juha Heinanen wrote:
Alex Hermann writes:
The issue is not with t_next_contacts, but with t_load_contacts. It is not
discarding the ruri of the request that made the request end up in
failure_route. Instead it is added again to the dset, where it obviously
doesn't belong.
--
Greetings,
Alex Hermann
I went over tm documentation again, but
couldn't find any setting or
function to reset/ignore ruri.
Maybe there is some internal state keeping track of the ruri changes. In
that case, i'll adjust the patch to use ruri only depending on that
state. Somebody will have to tell me where that state is kept though.
every time t_next_contacts() is called, it rewrites request uri with
first remaining contact and if there are other contacts with the same q
value, it appends then as branches.