web-sct 0.2.0 - Case 2.5 : Pass - 1 ms @ 2021-01-18T16:56:03.304Z
Case Description
Send ping with binary payload of 126 octets.
Case Expectation
Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.0-0.10.9 Host: 192.168.0.103:5555 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: SPZMucEhKgfvLyAHHL5Sjw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: XV6rMCrp4wDGZowjPNKMQDoEuZ0= Content-Length: 0
| Key | Value | Description |
| isServer | False | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | False | 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 | False | 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 | 1000 | 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 | Too long control frame data | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 31 | 1 | 31 |
| 148 | 1 | 148 |
| Total | 2 | 179 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 134 | 1 | 134 |
| 244 | 1 | 244 |
| Total | 3 | 386 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 8 | 1 |
| 9 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=e78093ff, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 89fe007ee78093ff197e6d01197e6d01197e6d01197e6d01197e6d01197e6d01197e6d01197e6d01197e6d01197e6d01197e
6d01197e6d01197e6d01197e6d01 ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 881d03ea546f6f206c6f6e6720636f6e74726f6c206672616d652064617461
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=False, MASK=None
0x03ea546f6f206c6f6e6720636f6e74726f6c206672616d652064617461
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=6858edc2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 88826858edc26bb0
009 TCP DROPPED BY PEER