lluv-websocket - Case 7.9.1 : Pass - 0 ms @ 2016-03-22T16:32:48.624Z

Case Description

Send close with invalid close code 0

Case Expectation

Clean close with protocol error code or drop TCP

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=236&agent=lluv-websocket HTTP/1.1

Host: 127.0.0.1:9001

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Key: DvYd7Ak08mkP+D/wCI0RGg==

Sec-WebSocket-Version: 13

Sec-WebSocket-Protocol: echo

Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

HTTP/1.1 101 Switching Protocols

Server: AutobahnTestSuite/0.7.1-0.10.0

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: H7d9uL5Z4BK4QSHliutdTwpZ9PE=

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

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
27	1	27
290	1	290
Total	2	317

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
169	1	169
Total	2	173

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323336266167656e743d6c6c75762d776562736f636b657420485454502f312e

               310d0a486f73743a203132372e30 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

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

003 TX OCTETS: 88020000

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 8895815e632b82b42a45f73f0f42e57e105fe02a1658a13d0c4fe4

006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=21, MASKED=True, MASK=3831356536333262

               0x03ea496e76616c69642073746174757320636f6465

007 TCP DROPPED BY ME