Autobahn WebSockets Testsuite Report
Autobahn WebSockets

async_echo_server - Case 4.2.3 : Pass - 0 ms @ 2017-01-28T01:22:12.370Z

Case Description

Send small text message, then send frame with reserved control Opcode = 13, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Case Outcome

Actual events match at least one expected.

Expected:
{'NON-STRICT': [], 'OK': [('message', u'Hello, world!', False)]}

Observed:
[('message', u'Hello, world!', False)]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1

User-Agent: AutobahnTestSuite/0.7.5-0.10.9

Host: 127.0.0.1:6000

Upgrade: WebSocket

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

Sec-WebSocket-Key: CVvkWRbORuMSbgxe6dT9cg==

Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols

Upgrade: websocket

Sec-WebSocket-Accept: lYS0ybLIIxgGXi7k5ueJN+1J/Do=

Server: async_echo_server

Connection: upgrade


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).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
414
15115
1561156
Total3175

Octets Transmitted by Chop Size

Chop SizeCountOctets
6212
818
19119
2401240
Total5279

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
91
131
Total4


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
               352d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a5365632d576562536f63 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=6b75aa9f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: 818d6b75aa9f2310c6f304598ae80407c6fb4a
004 TX FRAME : OPCODE=13, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=91f48bbd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 8d8091f48bbd
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=0c57444a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 89800c57444a
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 810d48656c6c6f2c20776f726c6421
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
               Hello, world!
011 RX OCTETS: 880203ea
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
               0x03ea
013 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=2a48ef91, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
014 TX OCTETS: 88822a48ef9129a0
015 TCP DROPPED BY PEER