-
As @Anisotrop remarked in comments in https://github.com/kaazing/gateway/pull/445, the server (wsn transport) continues to read incoming data after detecting that the incoming WebSocket frame size exc…
-
websocket appears to crash on receiving a close reason code of 1006:
`Error: Close code 1006 is not valid.
at WebSocketConnection.close (/---/node_modules/websocket/lib/WebSocketConnection.js:422…
-
When Gateway is acting as a client, if the server violates [RFC 6455](https://tools.ietf.org/html/rfc6455) by sending a masked frame(BINARY or TEXT), then Gateway (WsnConnector) just treats the messag…
-
See https://github.com/alexhultman/uWebSockets/issues/56
-
Are there any ways to deal with it?
EV: error in callback (ignoring): Payload is too big. Send shorter messages or increase max_payload_size at /usr/local/lib/perl5/site_perl/5.16/Protocol/WebSocke…
-
I can't produce clean closes (callback calls). Not when close is client initiated and not when close is server initiated.
Here is my findings so far:
When calling close SR_CLOSING is set as the read…
-
by **opennota**:
RFC 6455 states, that Ping frame payload is optional:
https://tools.ietf.org/html/rfc6455#section-5.5.2:
A Ping frame MAY include "Application data".
However, t…
-
This is probably more of a question, but doesn't this lack congestion control?
If client or server side is not able to keep with with processing of data then the only option is to stop reading from t…
-
by **aicommander**:
What steps will reproduce the problem?
0. Open a WebSocket which will be connected to Internet Explorer 11
1. Call WebSocket.Receive() without providing any data to receive
2. Wai…
-
Non-fatal Exception: com.neovisionaries.ws.client.WebSocketException: The end of the stream has been reached unexpectedly.
at com.neovisionaries.ws.client.WebSocketInputStream.readBytes(WebSock…