AutobahnServer - Case 4.2.3 : Non-Strict - 1 ms @ 2013-03-03T15:37:39Z
Case Description
Send small text message, then send frame with reserved control Opcode = 13, then send Ping.
Case Expectation
Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.
Case Outcome
Actual events match at least one expected.
Expected:
{'NON-STRICT': [], 'OK': [('message', 'Hello, world!', False)]}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.5.2-0.5.9 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: gDr8ucLIlYyV9M/PbRxs+g== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnPython/0.5.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: YSMRX2r7JUs4gymQeK3YhRAJN/E=
Key | Value | Description |
isServer | False | True, iff I (the fuzzer) am a server, and the peer is a client. |
closedByMe | False | True, iff I have initiated closing handshake (that is, did send close first). |
failedByMe | False | True, iff I have failed the WS connection (i.e. due to protocol error). Failing can be either by initiating closing handshake or brutal drop TCP. |
droppedByMe | False | True, iff I dropped the TCP connection. |
wasClean | False | True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
wasNotCleanReason | peer dropped the TCP connection without previous WebSocket closing handshake | When wasClean == False, the reason what happened. |
wasServerConnectionDropTimeout | False | When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True. |
wasOpenHandshakeTimeout | False | When performing the opening handshake, but the peer did not finish in time, this gets True. |
wasCloseHandshakeTimeout | False | When we initiated a closing handshake, but the peer did not respond in time, this gets True. |
localCloseCode | None | The close code I sent in close frame (if any). |
localCloseReason | None | The close reason I sent in close frame (if any). |
remoteCloseCode | None | The close code the peer sent me in close frame (if any). |
remoteCloseReason | None | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
159 | 1 | 159 |
Total | 1 | 159 |
Chop Size | Count | Octets |
6 | 2 | 12 |
19 | 1 | 19 |
239 | 1 | 239 |
Total | 4 | 270 |
Opcode | Count |
Total | 0 |
Opcode | Count |
1 | 1 |
9 | 1 |
13 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
322d302e352e390d0a486f73743a203132372e302e302e313a393030310d0a557067726164653a20576562536f636b65740d
0a436f6e6e656374696f6e3a20557067726164650d0a507261676d613a206e6f2d63616368650d0a43616368652d436f6e74
726f6c3a206e6f2d63616368650d0a5365632d576562536f636b65742d4b65793a206744723875634c496c597956394d2f50
625278732b673d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
507974686f6e2f302e352e390d0a557067726164653a20576562536f636b65740d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f636b65742d4163636570743a2059534d52583272374a55733467796d51654b3359685241
4a4e2f453d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=4b88ba2b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d4b88ba2b03edd64724a49a5c24fad64f6a
004 TX FRAME : OPCODE=13, FIN=True, RSV=0, MASK=f1ae5d74, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 8d80f1ae5d74
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, MASK=7e4e22f1, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 89807e4e22f1
008 FAIL CONNECTION AFTER 1.000000 sec
009 TCP DROPPED BY PEER