You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
I ran into the scenario where WS requests above 16KiB were causing the WS connection to close with code
1006
and reasonSocket Error: read ECONNRESET
.If I set
fragmentationThreshold
to > 16KiB or setfragmentOutgoingMessages
tofalse
, 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!
The text was updated successfully, but these errors were encountered: