-
Bug
-
Resolution: Fixed
-
P3: Somewhat important
-
5.14.0
-
None
-
-
1478c1dec (dev), 1656ea3b7 (6.10), 5672ee61f (6.9), fda9cfad8 (tqtc/lts-6.8)
I've first used the Echo Client & Server example [1], but it also happens when the client example is run against an official server like [2].
When close() is called in the client, it leads to:
1. Client: WebSocket Connection Close [FIN]
2. Client: TCP FIN
3. Server: WebSocket Connection Close [FIN]
4. Client: TCP RST
Expected: The websocket as well as the TCP connection are shut down properly.
[1] https://doc.qt.io/qt-5/qtwebsockets-echoserver-example.html
[2] ws://echo.websocket.org
- relates to
-
QTBUG-68552 QWebSocket SIGPIPE on QWebSocketPrivate::close due to Timeout
-
- Reported
-
For Gerrit Dashboard: QTBUG-81084 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
440865,7 | Wait for gracious shutdown | dev | qt/qtwebsockets | Status: MERGED | +2 | 0 |
664972,2 | Wait for gracious shutdown | 6.10 | qt/qtwebsockets | Status: MERGED | +2 | 0 |
665083,2 | Wait for gracious shutdown | 6.9 | qt/qtwebsockets | Status: MERGED | +2 | 0 |
665136,2 | Wait for gracious shutdown | tqtc/lts-6.8 | qt/tqtc-qtwebsockets | Status: MERGED | +2 | 0 |