-
Notifications
You must be signed in to change notification settings - Fork 25
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
Browser refreshing causes websocket server exception #49
Comments
That's not a bug, is it? The socket has been closed so you get an exception to notify you of that. |
It's such a subtle severe bug that at least two places have to be changed to make the example server not crashing when interacting with Karax websocket on page refreshing.
regarding the example server , it should be
and cannot avoid this issue in our own case: |
* NEP-1 fixes * opcode is now bitsize: 4 * implements change proposed in #49 * documentation improvements * masking key can be an array thanks to new define * undeprecate some procs * readme doc link now doesn't have version
* made Frame an object, the bools and the opcode are now bitfields * masking key can be an array with `-d:websocketStricterMaskingKey` * added error enum for server header verification * NEP-1 fixes * implements change proposed in #49 * documentation improvements * undeprecate some procs * readme doc link now doesn't have version in the link to ease updating versions
websocket-0.3.5 latest version
Everytime enters the index.html again causes
as a websocket opened on page loading and closed on leaving.
our websocket server code is as follows: http://ix.io/1yUB
The text was updated successfully, but these errors were encountered: