Autobahn WebSockets Testsuite Report
Autobahn WebSockets

ServerFrameworkServer/6.9 - Case 6.4.3 : Pass - 1000 ms @ 2017-11-02T08:51:02Z

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)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.5.5-0.5.14
Host: localhost:5050
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: DZOiK3fDnDNx7ezqf9GWOA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: mjn6y66zaZ2AsfkgLWcOFmUek88=


Closing Behavior

KeyValueDescription
isServerFalseTrue, 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.
wasCleanTrueTrue, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen 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.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1007The close code the peer sent me in close frame (if any).
remoteCloseReasonInvalid UTF8 encodingThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
26126
1291129
Total2155

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
616
818
11111
2401240
Total5269

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
Total1


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
               352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 TX OCTETS: 01957c215233
003 TX OCTETS: b29bb38ec5eed1fdc0efe7
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: c7eca1d2
007 DELAY 1.000000 sec for TAG B
008 RX OCTETS: 881803ef496e76616c6964205554463820656e636f64696e6700
009 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=24, MASKED=False, MASK=None
               0x03ef496e76616c6964205554463820656e636f64696e6700
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=c4c41414, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
011 TX OCTETS: 8882c4c41414c72c
012 TCP DROPPED BY PEER