21 Sep
2012
21 Sep
'12
4:28 p.m.
Daniel-Constantin Mierla writes:
the second is better in this case, because will avoid
a loop through
local sockets. Also, your case is very rare, the warning is good to spot
if someone changed the uri in route headers.
daniel,
sorry about the noise. there is already rr mod param
enable_socket_mismatch_warning
which can be used to globally turn off the warning. it is at the moment
good enough for me, but a parameter could be added later that also
disables looking for the socket in cases when it is known not to be found.
-- juha