Pawl/0.3 - Case 7.9.11 : Pass - 4 ms @ 2017-10-12T00:31:29.993Z

Case Description

Send close with invalid close code 2999

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=246&agent=Pawl/0.3 HTTP/1.1
Host: 127.0.0.1:9001
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: ZG43c21mM0ZiRjcwPXBEbw==
User-Agent: Ratchet-Pawl/0.2.3
Origin: http://127.0.0.1

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.6-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: 3l7IOVUhqBtkcC5Jboh6T+BY7Gc=

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 WebSocket 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	2999	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	Ratchet detected an invalid close code	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
46	1	46
242	1	242
Total	2	288

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
206	1	206
Total	2	210

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: 474554202f72756e436173653f636173653d323436266167656e743d5061776c2f302e3320485454502f312e310d0a486f73

               743a203132372e302e302e313a39 ...

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

               0x0bb7

003 TX OCTETS: 88020bb7

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 88a83b4e243b38a4765a4f2d4c5e4f6e405e4f2b474f5e2a045a556e4d554d2f48525f6e4757543d411b5821405e

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

               0x03ea5261746368657420646574656374656420616e20696e76616c696420636c6f736520636f6465

007 TCP DROPPED BY ME