Autobahn WebSockets Testsuite Report
Autobahn WebSockets

PocketSocketClient - Case 6.4.4 : Pass - 1003 ms @ 2016-03-30T11:13:47.087Z

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=PocketSocketClient HTTP/1.1
Host: localhost:9001
Sec-WebSocket-Key: j6j6BssNzkS3j67aAuGsFw==
Sec-WebSocket-Version: 13
Upgrade: websocket
Origin: http://localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Connection: upgrade
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.5-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: DtUpFX3CFVlcXJF9LFJLARxjRpM=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanFalseTrue, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonpeer dropped the TCP connection without previous WebSocket closing handshakeWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCodeNoneThe close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCodeNoneThe close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
2991299
Total1299

Octets Transmitted by Chop Size

Chop SizeCountOctets
111
212
12112
2061206
Total4221

Frames Received by Opcode

OpcodeCount
Total0

Frames Transmitted by Opcode

OpcodeCount
Total0


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3737266167656e743d636f6d2e7a776f70706c652e5053576562536f636b6574
               20485454502f312e310d0a486f73 ...
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 TCP DROPPED BY PEER