3 Sep
2009
3 Sep
'09
11:29 a.m.
On 03.09.2009 11:19 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
daniel,
i didn't quite understand, which behavior you refer to. the problem
that i reported was related to un-true error message, because
stateless_reply onreply_route has been defined.
i don't remember where i got the above example, i.e., if it came from k
or sr lists.
not from K -- there were no routes with string names.
So you refer to warning message you got -- I thought that reply is not
dropped.
Cheers,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/
onreply_route [stateless_reply] { # process transactionless replies
xlog("L_NOTICE", "Reply from $si does not belong to
transaction\n");
return 0; # 0 == drop
}
if i remember correctly, this used to work at some point, but not
anymore.
In K drop() forked discard of replies. exit() which is equivalent of
"return 0" just terminates the execution of route and relays the reply.
This behavior will be there very soon.