Autobahn WebSockets Testsuite Report
Autobahn WebSockets

Microsoft-HTTPAPI/2.0 - Case 5.4 : Pass - 1052 ms @ 2021-01-02T08:46:03.823Z

Case Description

Send text Message fragmented into 2 fragments, octets are sent in frame-wise chops.

Case Expectation

Message is processed and echo'ed back to us.

Case Outcome

Actual events match at least one expected.

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

Observed:
[('message', u'fragment1fragment2', False)]

Case Closing Behavior

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



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.7.5-0.10.9
Host: 127.0.0.1:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: QPCL7mIlYOd0VDClYN2Cjw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Server: Microsoft-HTTPAPI/2.0
Connection: Upgrade
Sec-WebSocket-Accept: 2sGkjgc/SIgZ4eH+8E7RD7E5fFU=
Date: Sat, 02 Jan 2021 16:46:03 CST


Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, 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.
wasCleanFalseTrue, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonserver did not drop TCP connection (in time)When wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutTrueWhen 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).
remoteCloseCodeNoneThe 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
212
11222
1971197
Total4221

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
15230
2401240
Total4278

Frames Received by Opcode

OpcodeCount
01
11
81
Total3

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
               352d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a5365727665723a204d69 ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=37355bcd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
               fragment1
003 TX OCTETS: 018937355bcd51473aaa5a5035b906
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=30194064, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
               fragment2
005 CLOSE CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 808930194064566b21035d7c2e1002
007 RX OCTETS: 0109667261676d656e7431
008 RX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASKED=False, MASK=None
               fragment1
009 RX OCTETS: 8009667261676d656e7432
010 RX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASKED=False, MASK=None
               fragment2
011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=0094e6fd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
012 TX OCTETS: 88820094e6fd037c
013 RX OCTETS: 8800
014 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
015 CLOSING CONNECTION
016 TCP DROPPED BY ME