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

Issue on the WebSocket library #1416

Closed
giorgiogalantegit opened this issue Jul 12, 2018 · 2 comments
Closed

Issue on the WebSocket library #1416

giorgiogalantegit opened this issue Jul 12, 2018 · 2 comments

Comments

@giorgiogalantegit
Copy link

We start to test the websocket library with enabled SSL by using simple websocket server make by using node js 8.11.3 and express-ws 4.0.0.

when the client try to complete the connection the server crash with this error code:

RangeError: Invalid WebSocket frame: FIN must be set

Looking into the library I see that during the connecting a ping message is sent.
The ping can be send only after the connection has been establish. We just comment this line and the connection complete without error..
We start to receive message from the client, but as soon as the client close the connection the server crash again. we see the close method send 2 byte 0x87, 0x00. For my knowing for close the connection, the code is just a single byte equal to 0x8. We made also this update and also the close work properly.

the remain issue that I not was able to figure out are that if I send a ping or a message from the server to the client this replay in a manner that let crash again the server.
We are using nodejs
Kind regard

@slaff
Copy link
Contributor

slaff commented Jul 12, 2018

You can try the still unfinished websocket refactoring in that PR: #1387.

@Morbden
Copy link

Morbden commented Oct 27, 2018

#1324 (comment)

This is the solution to the FIN error. But it should be correct already in the release.

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

3 participants