Open dbrgn opened 7 years ago
I'd only do that in debug mode though.
@lgrahl the Java version implements that currently:
Do you think it should be removed?
I think it should be active in debug mode only.
Reason? Performance?
No, I just want to be cautious when giving out detailed error reasons. Think of the padding oracle attack on SSL.
I misinterpreted this thread's topic (dunno why). Sure, logging these messages should be fine.
What I was referring to was WebSocket close code reasons.
...so that when logging a send-error message, we actually know which message was lost.