From be4bfc5feeb61e97378bee325d36bb74f007fe04 Mon Sep 17 00:00:00 2001 From: Kai Koehne Date: Thu, 7 Apr 2016 09:52:29 +0200 Subject: Doc: Add external-resources.qdoc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Also sanitize some linking, e.g. by referencing to the paper by title, not by link. Change-Id: I95482994ca569001a23a3beb0e3cbe6739f4ed77 Reviewed-by: Leena Miettinen Reviewed-by: Topi Reiniö --- src/websockets/qwebsocketserver.cpp | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'src/websockets/qwebsocketserver.cpp') diff --git a/src/websockets/qwebsocketserver.cpp b/src/websockets/qwebsocketserver.cpp index 49d8799..ff64f3e 100644 --- a/src/websockets/qwebsocketserver.cpp +++ b/src/websockets/qwebsocketserver.cpp @@ -60,17 +60,16 @@ Calling close() makes QWebSocketServer stop listening for incoming connections. QWebSocketServer currently does not support - \l {http://tools.ietf.org/html/rfc6455#page-39} {extensions} and - \l {http://tools.ietf.org/html/rfc6455#page-12} {subprotocols}. + \l {WebSocket Extensions} and + \l {WebSocket Subprotocols}. - \note When working with self-signed certificates, FireFox currently has a - \l {https://bugzilla.mozilla.org/show_bug.cgi?id=594502} {bug} that prevents it to + \note When working with self-signed certificates, \l{Firefox bug 594502} prevents \l{Firefox} to connect to a secure WebSocket server. To work around this problem, first browse to the secure WebSocket server using HTTPS. FireFox will indicate that the certificate is invalid. From here on, the certificate can be added to the exceptions. After this, the secure WebSockets connection should work. - QWebSocketServer only supports version 13 of the WebSocket protocol, as outlined in RFC 6455. + QWebSocketServer only supports version 13 of the WebSocket protocol, as outlined in \l{RFC 6455}. \sa {WebSocket Server Example}, QWebSocket */ -- cgit v1.2.1