WebSocket-Node icon indicating copy to clipboard operation
WebSocket-Node copied to clipboard

Connection closes if fragmentation is attempted

Open fabioberger opened this issue 6 years ago • 3 comments

I ran into the scenario where WS requests above 16KiB were causing the WS connection to close with code 1006 and reason Socket Error: read ECONNRESET.

If I set fragmentationThreshold to > 16KiB or set fragmentOutgoingMessages to false, the connection remains open and the request completes successfully.

This leads me to several questions:

Is this expected behavior? If not, what is causing it? What are the implications of disabling fragmentation? Is there some other upper threshold on the size of a fragment I should be aware of?

Environment: Node.js v11.15.0

Thanks in advance for any help!

fabioberger avatar Jul 12 '19 15:07 fabioberger

@theturtle32 any thoughts on this?

fabioberger avatar Sep 06 '19 16:09 fabioberger

Bump on this

fabioberger avatar Feb 19 '20 19:02 fabioberger

Have you found more info on this?

jespertheend avatar May 02 '21 19:05 jespertheend