AutobahnServer - Case 7.1.4 : Pass - 1 ms @ 2013-03-03T15:37:45Z

Case Description

Send text message after sending a close frame.

Case Expectation

Clean close with normal code. Text message ignored.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1

User-Agent: AutobahnTestSuite/0.5.2-0.5.9

Host: 127.0.0.1:9001

Upgrade: WebSocket

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

Sec-WebSocket-Key: CZgTsMlf673l2A9pvhU/OA==

Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols

Server: AutobahnPython/0.5.9

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: q5wv+5lz+uiudfA4chaldbx3sYc=


Closing Behavior

KeyValueDescription
isServerFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSockets 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
414
1591159
Total2163

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
18118
2391239
Total3265

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
               322d302e352e390d0a486f73743a203132372e302e302e313a393030310d0a557067726164653a20576562536f636b65740d
               0a436f6e6e656374696f6e3a20557067726164650d0a507261676d613a206e6f2d63616368650d0a43616368652d436f6e74
               726f6c3a206e6f2d63616368650d0a5365632d576562536f636b65742d4b65793a20435a6754734d6c663637336c32413970
               7668552f4f413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               507974686f6e2f302e352e390d0a557067726164653a20576562536f636b65740d0a436f6e6e656374696f6e3a2055706772
               6164650d0a5365632d576562536f636b65742d4163636570743a20713577762b356c7a2b756975646641346368616c646278
               337359633d0d0a0d0a
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=03fe1b28, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
003 TX OCTETS: 888203fe1b280016
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=84a1a6a2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello World!
005 TX OCTETS: 818c84a1a6a2ccc4caceeb81f1cdf6cdc283
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 880203e8
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
009 TCP DROPPED BY PEER