Roy T. Fielding wrote:
> I can certainly understand that :) Here is a new patch along those
> lines.
+1, but you might want to reduce the severity on those error messages
if this is actually a common occurrence. After all, there is nothing
that the server can do about it, and the client won't be complaining,
though it is still useful info for looking at DoS attacks.
I'll lower the severity of both the getsockname msg and the TCP_NODELAY
msg to debug (the former is currently error, the latter is currently
warning)... if the connection had lasted just a wee bit longer, we
wouldn't have logged anything anyway.
Thanks as always...
