WebSockets Protocol Test Report
Autobahn WebSockets

AutobahnClient/0.4.10 - Case 5.2 : Pass - 1 ms @ 2012-01-09T14:53:45Z

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 /runCase?case=46&agent=AutobahnClient/0.4.10 HTTP/1.1
User-Agent: AutobahnWebSockets/0.4.10
Host: localhost:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: d9JtwgkKtwW1I+GCPdbp6w==
Sec-WebSocket-Version: 8
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSocketsTestSuite/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: JWetvfuh1RJceiy6BYg+FFtT304=


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.
droppedByMeTrueTrue, 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.
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).
remoteCloseReasonfragmented control frameThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
32132
2341234
Total2266

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
11222
1731173
Total4199

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
81
101
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3436266167656e743d4175746f6261686e436c69656e742f302e342e31302048
               5454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b6574732f302e342e31300d0a486f
               73743a206c6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e
               3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2064394a7477676b4b74775731492b474350646270
               36773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a20380d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
               6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a204a5765747666756831
               524a63656979364259672b464674543330343d0d0a0d0a
002 TX FRAME : OPCODE=10, FIN=False, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment1
003 TX OCTETS: 0a09667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment2
005 TX OCTETS: 8009667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 889a924d7e5991a7182bf32a133cfc391b3db22e1137e63f1135b22b0c38ff28
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=924d7e59
               źfragmented control frame
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME