-
There are several test scenarios where client needs to close the underlying tcp connection after websocket upgrade without doing a websocket close handshake. This is mandated by RFC 6455 for cases lik…
-
```
ERROR - EngineUtils: Error in Handshake: Draft #'13' not supported.
Is it possible to fall back to Flash in these cases regardless of the browser
in question?
```
Original issue reported on cod…
-
This seems wrong?
-
As far as I understand, when `WebsocketClientProtocol.close()` is called, the closing handshake starts (client sends the FIN packet), and waits until the peer acknowledges (also sends FIN) and closes …
-
```
What steps will reproduce the problem?
1. Try to close a websocket with 'None' as code
What is the expected output? What do you see instead?
RFC 6455 says "When sending a Close frame in respons…
-
The current code base is pretty careful to check and handle the various RFC 6455 requirements, which is a good thing.
However, what it does when it detects a failure is incorrect.
First off, it atte…
-
```
What steps will reproduce the problem?
1. Try to close a websocket with 'None' as code
What is the expected output? What do you see instead?
RFC 6455 says "When sending a Close frame in respons…
-
Just installed shinysdr, using a nooElec dongle and the server fires up fine however, when the first client connects, it traps as follows:
INFO:shinysdr:127.0.0.1 - - [21/Jan/2015:11:11:41 +0000] "GE…
-
The Autobahn library [doesn't have support for the `wss` protocol](https://github.com/tavendo/AutobahnAndroid/issues/8) so either switch to another library or wait until the feature is added
ocram updated
8 years ago
-
Here is the log from @ahousing:
```
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Kaazing iOS Client ..........................…