Autobahn WebSocket Testsuite Report
Autobahn WebSocket

wtx - Case 5.4 : Pass - 1 ms @ 2023-09-27T21:03:39.791Z

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

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=48&agent=wtx HTTP/1.1
Connection: Upgrade
Host: 127.0.0.1:9080
Sec-WebSocket-Key: dJxjlMjqIevlPlkgw+N3gA==
Sec-WebSocket-Version: 13
Upgrade: websocket
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=12; server_max_window_bits=12; client_no_context_takeover; server_no_context_takeover
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: FJZgjPrbja0pxZgNhZ3fRRuRbco=


Closing Behavior

KeyValueDescription
isServerTrueTrue, 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.
wasCleanTrueTrue, iff full WebSocket 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).
remoteCloseCode1000The 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
818
24124
3341334
Total3366

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
11222
2061206
Total4232

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3438266167656e743d77747820485454502f312e310d0a436f6e6e656374696f
               6e3a20557067726164650d0a486f ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
               fragment1
003 TX OCTETS: 0109667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
               fragment2
005 CLOSE CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 8009667261676d656e7432
007 RX OCTETS: 8192ed509c608b22fd078035f214dc36ee018a3df90e9962
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=18, MASKED=True, MASK=6564353039633630
               fragment1fragment2
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 880203e8
011 RX OCTETS: 888225406de726a8
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3235343036646537
               0x03e8
013 TCP DROPPED BY ME