7 Nov
2013
7 Nov
'13
5:25 p.m.
Julius Plenz wrote:
Worse still, if my first home server is not responding, then it seems the proxied packet never leaves the wait_a_bit() loop and I get an error like
WARNING: Unresponsive thread 0 for request 0, in component <core> module
I'll take a look. The fix should be simple.
What is the server's "exit strategy" in case there is no live home server?
Post-proxy-type "fail".
I would say "send a reject", but then at some point the server NEEDS to call post_proxy_fail_handler(request) and initiate a cleanup. I cannot see where this is happening.
It should be there... Alan DeKok.