18 Apr
2013
18 Apr
'13
6:40 p.m.
Hello,
On 4/18/13 5:30 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
ok, so it is
indeed not a change that could create such trouble.
Cheers,
Daniel
is the proxy listening on 10080?
yes, my
proxy is listening on 10080 for websocket connections.
I haven't looked yet at the chance to return
2, but when I did the work
for gruu, some changes were done to rr module not to detect as strict
routing and everything seemed fine for this case.
i added return of 2 (instead of
1) when route calculation based on
userpart of route succeeded.
Can you test with a version before the return 2
addition just to see if
the $du is set?
i don't have such a source available anymore but the commit
didn't do
anything else but returned 2 instead of 1 in one particular case.
now that $du gets set, it gets set with wrong uri and my proxy cannot
get the ack forwarded. it works ok if i just set $du="" immediately after
loose_route() call.
-- juha
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda