Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
5.14.0
-
None
Description
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
Attachments
Issue Links
- relates to
-
QTBUG-68552 QWebSocket SIGPIPE on QWebSocketPrivate::close due to Timeout
- Reported
Gerrit Reviews
For Gerrit Dashboard: QTBUG-81084 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
440865,5 | WIP: Don't immediately close the underlying TCP socket | dev | qt/qtwebsockets | Status: NEW | -2 | 0 |