AutobahnServer/0.4.10 - Case 5.10 : Pass - 1 ms @ 2012-01-09T14:43:12Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in per-frame chops.
Case Expectation
The connection is failed immediately, since there is no message to continue.
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: AutobahnWebSocketsTestSuite/0.4.10 Host: localhost:9000 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: DBpoIOZaCIvJC1hkabExxA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSockets/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: zX3fhZ9esUfraky/p2a+hvSP4Qs=
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. |
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 | received continuation data frame outside fragmented message | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
63 | 1 | 63 |
164 | 1 | 164 |
Total | 2 | 227 |
Chop Size | Count | Octets |
8 | 1 | 8 |
19 | 1 | 19 |
30 | 1 | 30 |
201 | 1 | 201 |
Total | 4 | 258 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
1 | 1 |
8 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a204442706f
494f5a614349764a4331686b6162457878413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
20557067726164650d0a5365632d576562536f636b65742d4163636570743a207a583366685a396573556672616b792f7032
612b687653503451733d0d0a0d0a
002 TX FRAME : OPCODE=0, FIN=True, RSV=0, MASK=afd03e3a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
non-continuation payload
003 TX OCTETS: 8098afd03e3ac1bf5017ccbf504ec6be4b5bdbb951548fa05f43c3bf5f5e
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=6432c014, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 818d6432c0142c57ac780b1ee0630b40ac7045
007 RX OCTETS: 883d03ea726563656976656420636f6e74696e756174696f6e2064617461206672616d65206f75747369646520667261676d
656e746564206d657373616765
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
êreceived continuation data frame outside fragmented message
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=00872ab3, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
010 TX OCTETS: 888200872ab3036f
011 TCP DROPPED BY PEER