Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection closes if fragmentation is attempted #359

Open
fabioberger opened this issue Jul 12, 2019 · 3 comments
Open

Connection closes if fragmentation is attempted #359

fabioberger opened this issue Jul 12, 2019 · 3 comments

Comments

@fabioberger
Copy link

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
Copy link
Author

@theturtle32 any thoughts on this?

@fabioberger
Copy link
Author

Bump on this

@jespertheend
Copy link

Have you found more info on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants