AutobahnServer - Case 6.4.3 : Pass - 2001 ms @ 2017-11-02T08:57:14Z
Case Description
Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564
Case Expectation
The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.
Case Outcome
Actual events match at least one expected.
Expected:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}
Observed:
[('timeout', 'A')]
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: qYLMgcjU8lIbOmAuYgnKbQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnPython/0.5.14 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: /TBJgUZh6owriKFp0xnIBTCe0y4=
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 | 1007 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | encountered invalid UTF-8 while processing text message at payload octet index 12 | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
85 | 1 | 85 |
160 | 1 | 160 |
Total | 2 | 245 |
Chop Size | Count | Octets |
4 | 1 | 4 |
6 | 1 | 6 |
8 | 1 | 8 |
11 | 1 | 11 |
240 | 1 | 240 |
Total | 5 | 269 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
8 | 1 |
Total | 1 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
507974686f6e2f302e352e31340d ...
002 TX OCTETS: 0195d9aed90c
003 TX OCTETS: 171438b160615ac265606c
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: f8492e59
007 DELAY 1.000000 sec for TAG B
008 RX OCTETS: 885303ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e6720746578
74206d6573736167652061742070 ...
009 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=83, MASKED=False, MASK=None
0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874
206d65737361676520617420706179 ...
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=9d720db0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
011 TX OCTETS: 88829d720db09e9a
012 DELAY TIMEOUT on TAG B
013 TCP DROPPED BY PEER