AutobahnServer/0.4.10 - Case 5.18 : Pass - 1 ms @ 2012-01-09T14:43:12Z
Case Description
Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.
Case Expectation
The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnWebSocketsTestSuite/0.4.10 Host: localhost:9000 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: stuaBk6WuUnnS2cxV6jHnQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSockets/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: iAn1b+63K3sR02R789K4MDrO8ts=
| 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 | True | True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
| wasNotCleanReason | None | 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. |
| wasCloseHandshakeTimeout | False | When we initiated a closing handshake, but the peer did not respond in time, this gets True. |
| localCloseCode | 1000 | The close code I sent in close frame (if any). |
| localCloseReason | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | 1002 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | received non-continuation data frame while inside fragmented message | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 72 | 1 | 72 |
| 164 | 1 | 164 |
| Total | 2 | 236 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 15 | 2 | 30 |
| 201 | 1 | 201 |
| Total | 4 | 239 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 2 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2073747561
426b365775556e6e5332637856366a486e513d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
20557067726164650d0a5365632d576562536f636b65742d4163636570743a2069416e31622b36334b337352303252373839
4b344d44724f3874733d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, MASK=e8a45e10, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0189e8a45e108ed63f7785c13064d9
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=dd94a6d6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8189dd94a6d6bbe6c7b1b0f1c8a2ef
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 884603ea7265636569766564206e6f6e2d636f6e74696e756174696f6e2064617461206672616d65207768696c6520696e73
69646520667261676d656e746564206d657373616765
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
êreceived non-continuation data frame while inside fragmented message
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=d2b385a0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
010 TX OCTETS: 8882d2b385a0d15b
011 TCP DROPPED BY PEER