Autobahn WebSocket Testsuite Report
Autobahn WebSocket

deflate-client - Case 7.13.1 : Informational - 5 ms @ 2023-02-24T01:28:09.802Z

Case Description

Send close with close code 5000

Case Expectation

Actual events are undefined by the spec.

Case Outcome

Actual events are undefined by the spec.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (INFORMATIONAL)



Opening Handshake

GET /runCase?case=245&agent=deflate-client HTTP/1.1
Host: localhost:9002
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Key: h/70wYnTZrQwMhi+RANfNw==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: permessage-deflate;client_max_window_bits=9;server_max_window_bits=9
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: Z/CXSwvkWBVAUb358f4OTI5pvx4=


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.
localCloseCode5000The 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).
remoteCloseReasoninvalid close code 5000The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
31131
2861286
Total2317

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
2061206
Total2210

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
Total1


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323435266167656e743d6465666c6174652d636c69656e7420485454502f312e
               310d0a486f73743a206c6f63616c ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x1388
003 TX OCTETS: 88021388
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 88999ca175989f4b1cf6eac019f1f88116f4f3d210b8ffce11fdbc9445a8ac
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=25, MASKED=True, MASK=3963613137353938
               0x03ea696e76616c696420636c6f736520636f64652035303030
007 TCP DROPPED BY ME