yawl - Case 6.1.2 : Fail - 2001 ms @ 2014-11-25T21:29:39.739Z

Case Description

Send fragmented text message, 3 fragments each of length 0.

Case Expectation

A message is echo'ed back to us (with empty payload).

Case Outcome

Actual events differ from any expected.

Expected:
{'OK': [('message', u'', False)]}

Observed:
[]

Case Closing Behavior

The spec requires the connection to be failed cleanly here (UNCLEAN)

Opening Handshake

GET /runCase?case=66&agent=yawl HTTP/1.1
Connection: keep-alive, Upgrade
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: XSu/U/30A9O12Hx6qAZrdQ==
Host: localhost:9001

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.1-0.9.3-3
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: wpr45T/k58Dp+pAvlr7UiuJ5rZs=

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	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	False	True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer did not respond (in time) in closing handshake	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	True	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	None	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
234	1	234
Total	1	234

Octets Transmitted by Chop Size

Chop Size	Count	Octets
2	4	8
170	1	170
Total	5	178

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
0	2
1	1
8	1
Total	4

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3636266167656e743d7961776c20485454502f312e310d0a436f6e6e65637469

               6f6e3a206b6565702d616c697665 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

003 TX OCTETS: 0100

004 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

005 TX OCTETS: 0000

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

007 TX OCTETS: 8000

008 CLOSE CONNECTION AFTER 1.000000 sec

009 CLOSING CONNECTION

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

011 TX OCTETS: 8800

012 TCP DROPPED BY ME