ServerFrameworkServer/6.9 - Case 5.18 : Pass - 1 ms @ 2017-11-02T08:50:58Z
Case Description
Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.
Case Expectation
The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.
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.5.5-0.5.14 Host: localhost:5050 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: TZqcs8hmrznZXygEznB6fA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: uMFwdpbrHq+GRN/kFfCrG7rNjVI=
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 WebSockets 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 | Unexpected frame byte when receiving a framented frame 0x81 | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
64 | 1 | 64 |
129 | 1 | 129 |
Total | 2 | 193 |
Chop Size | Count | Octets |
8 | 1 | 8 |
15 | 2 | 30 |
240 | 1 | 240 |
Total | 4 | 278 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
1 | 2 |
8 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=327e78c0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7431
003 TX OCTETS: 0189327e78c0540c19a75f1b16b403
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=a380be60, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7432
005 TX OCTETS: 8189a380be60c5f2df07cee5d01491
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 883e03ea556e6578706563746564206672616d652062797465207768656e20726563656976696e672061206672616d656e74
6564206672616d65203078383100 ...
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=62, MASKED=False, MASK=None
0x03ea556e6578706563746564206672616d652062797465207768656e20726563656976696e672061206672616d656e7465
64206672616d65203078383100 ...
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=ef6d2952, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882ef6d2952ec85
011 TCP DROPPED BY PEER