SwiftWebSocket - Case 6.4.4 : Pass - 1001 ms @ 2016-04-13T16:10:22.570Z

Case Description

Same as Case 6.4.2, but we send message not in 3 frames, but in 3 chops of the same message frame.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 =

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)

Opening Handshake

GET /runCase?case=77&agent=SwiftWebSocket HTTP/1.1
Host: localhost:9001
Origin: ws://localhost:9001/runCase?case=77&agent=SwiftWebSocket
Sec-WebSocket-Version: 13
User-Agent: SwiftWebSocket
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: 52pR/C6WdAka6QKqwwEuIg==

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: VizNyCQaRiO0D9CtYEBzrLKy/nE=

Closing Behavior

Key	Value	Description
isServer	True	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	True	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	Payload error	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
21	1	21
283	1	283
Total	2	304

Octets Transmitted by Chop Size

Chop Size	Count	Octets
1	1	1
2	1	2
4	1	4
12	1	12
206	1	206
Total	5	225

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3737266167656e743d5377696674576562536f636b657420485454502f312e31

               0d0a486f73743a206c6f63616c68 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 TX OCTETS: 0115

003 TX OCTETS: cebae1bdb9cf83cebcceb5f4

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: 90

007 DELAY 1.000000 sec for TAG B

008 RX OCTETS: 888f0a84878e096bd7ef73e8e8ef6ea4e2fc78ebf5

009 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=15, MASKED=True, MASK=3061383438373865

               0x03ef5061796c6f6164206572726f72

010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

011 TX OCTETS: 880203e8

012 TCP DROPPED BY ME