Autobahn WebSockets Testsuite Report
Autobahn WebSockets

ServerFrameworkServer/6.6.5 - Case 5.2 : Pass - 1 ms @ 2017-11-02T08:53:24Z

Case Description

Send Pong fragmented into 2 fragments.

Case Expectation

Connection is failed immediately, since control message MUST NOT be fragmented.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

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:5051
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: 61B3hrU4CTdvQm8KBN2Yhg==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: I6yfKTc5G9Hd1CHhUcqFkHAtHp0=


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).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasonControl frames cannot be fragmented: 0xaThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
45145
1291129
Total2174

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
15230
2401240
Total4278

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
81
101
Total3


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
               352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=10, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=967d767e, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x667261676d656e7431
003 TX OCTETS: 0a89967d767ef00f1719fb18180aa7
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=4c99b19b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x667261676d656e7432
005 TX OCTETS: 80894c99b19b2aebd0fc21fcdfef7e
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 882b03ea436f6e74726f6c206672616d65732063616e6e6f7420626520667261676d656e7465643a2030786100
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=43, MASKED=False, MASK=None
               0x03ea436f6e74726f6c206672616d65732063616e6e6f7420626520667261676d656e7465643a2030786100
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=7e408876, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 88827e4088767da8
011 TCP DROPPED BY PEER