AutobahnServer - Case 5.18 : Pass - 1 ms @ 2017-11-02T08:57:10Z
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: AutobahnTestSuite/0.5.5-0.5.14 Host: localhost:9000 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: oJ6Qcrqvgoj4GO+wLXnZdw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnPython/0.5.14 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: ASR3vAsmYkHYQsStQrWcl1RQSMc=
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. |
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 | 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 |
160 | 1 | 160 |
Total | 2 | 232 |
Chop Size | Count | Octets |
8 | 1 | 8 |
15 | 2 | 30 |
240 | 1 | 240 |
Total | 4 | 278 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
1 | 2 |
8 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
507974686f6e2f302e352e31340d ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=fec88ed6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7431
003 TX OCTETS: 0189fec88ed698baefb193ade0a2cf
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=40ecbf7f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7432
005 TX OCTETS: 818940ecbf7f269ede182d89d10b72
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 884603ea7265636569766564206e6f6e2d636f6e74696e756174696f6e2064617461206672616d65207768696c6520696e73
69646520667261676d656e746564 ...
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=70, MASKED=False, MASK=None
0x03ea7265636569766564206e6f6e2d636f6e74696e756174696f6e2064617461206672616d65207768696c6520696e7369
646520667261676d656e746564206d ...
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=cc1c8e80, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882cc1c8e80cff4
011 TCP DROPPED BY PEER