Firefox/16.0-20100101 - Case 7.9.3 : Fail - 1 ms @ 2012-10-12T12:38:43Z
Case Description
Send close with invalid close code 1004
Case Expectation
Clean close with protocol error code or drop TCP
Case Outcome
The close code should have been 1002 or empty
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
The close code should have been 1002 or empty (WRONG CODE)
GET /runCase?case=228&agent=Firefox/16.0-20100101 HTTP/1.1 Host: localhost:9001 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20100101 Firefox/16.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Connection: keep-alive, Upgrade Sec-WebSocket-Version: 13 Origin: http://localhost:8080 Sec-WebSocket-Key: qBXzN32xl8+wa7kGEBDEjw== Pragma: no-cache Cache-Control: no-cache Upgrade: websocket
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.5.2-0.5.8 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: PCTQ6zgUtaHk9SOfBQBJM1ctki4=
Key | Value | Description |
isServer | True | True, iff I (the fuzzer) am a server, and the peer is a client. |
closedByMe | True | True, iff I have initiated closing handshake (that is, did send close first). |
failedByMe | True | 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 | True | 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 | 1004 | The close code I sent in close frame (if any). |
localCloseReason | None | The close reason I sent in close frame (if any). |
remoteCloseCode | 1004 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | None | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
8 | 1 | 8 |
516 | 1 | 516 |
Total | 2 | 524 |
Chop Size | Count | Octets |
4 | 1 | 4 |
168 | 1 | 168 |
Total | 2 | 172 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
8 | 1 |
Total | 1 |
000 RX OCTETS: 474554202f72756e436173653f636173653d323238266167656e743d46697265666f782f31362e302d323031303031303120
485454502f312e310d0a486f73743a206c6f63616c686f73743a393030310d0a557365722d4167656e743a204d6f7a696c6c
612f352e3020284d6163696e746f73683b20496e74656c204d6163204f5320582031302e383b2072763a31362e3029204765
636b6f2f32303130303130312046697265666f782f31362e300d0a4163636570743a20746578742f68746d6c2c6170706c69
636174696f6e2f7868746d6c2b786d6c2c6170706c69636174696f6e2f786d6c3b713d302e392c2a2f2a3b713d302e380d0a
416363657074 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e352e322d302e352e380d0a557067726164653a20576562536f636b65740d0a436f6e6e656374
696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a2050435451367a67557461486b3953
4f664251424a4d3163746b69343d0d0a0d0a
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
ì
003 TX OCTETS: 880203ec
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8882a8ae1e46ab42
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=6138616531653436
ì
007 TCP DROPPED BY ME