guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Jumper <mike.jum...@guac-dev.org>
Subject Re: WebSockets enablement issue --> SSL Scanning issue
Date Wed, 22 Mar 2017 01:06:12 GMT
The tutorial hasn't been updated with respect to WebSocket, and still only
describes how to set up the HTTP tunnel. If you want to add WebSocket
support to your Guacamole-driven application, you will need to add an
implementation of GuacamoleWebSocketTunnelEndpoint (the WebSocket anology
to GuacamoleHTTPTunnelServlet):

http://guacamole.incubator.apache.org/doc/guacamole-common/org/apache/guacamole/websocket/GuacamoleWebSocketTunnelEndpoint.html

Beware that Java support for WebSockets is different from servlets. If
you're already experienced with using Java servlets, WebSocket endpoints
will have bit of a learning curve. Definitely give it a shot and let us
know if you run into any trouble while you do. Perhaps we can use that
feedback to update the tutorial.

By the way, the dev@ mailing list is a better place for development
discussion, rather than the Nabble interface to the user@ list:

http://guacamole.incubator.apache.org/support/#mailing-lists

- Mike

On Tue, Mar 21, 2017 at 2:02 PM, bsavard <bsavard@zmartests.com> wrote:

> I tried again using a vanilla setup with the tutorial and I'm still getting
> the same issue. No WebSocket.
>
> With the Tutorial, I'm getting the following sequence in tomcat access log.
> "GET /tutorial/index.html HTTP/1.1" 304 -
> "POST /tutorial/tunnel?connect HTTP/1.1" 200 36
> "POST /tutorial/tunnel?write:97c6e4c5-b86a-4ede-9961-daa9be5b728c
> HTTP/1.1"
> 200 -
> "GET /tutorial/tunnel?read:97c6e4c5-b86a-4ede-9961-daa9be5b728c:0
> HTTP/1.1"
> 200 639
> "POST /tutorial/tunnel?write:97c6e4c5-b86a-4ede-9961-daa9be5b728c
> HTTP/1.1"
> 200 -
> "GET /tutorial/tunnel?read:97c6e4c5-b86a-4ede-9961-daa9be5b728c:1
> HTTP/1.1"
> 200 8217
> "GET /tutorial/tunnel?read:97c6e4c5-b86a-4ede-9961-daa9be5b728c:2
> HTTP/1.1"
> 200 23377
> "POST /tutorial/tunnel?write:97c6e4c5-b86a-4ede-9961-daa9be5b728c
> HTTP/1.1"
> 200 -
> "POST /tutorial/tunnel?write:97c6e4c5-b86a-4ede-9961-daa9be5b728c
> HTTP/1.1"
> 200 -
> ....
>
>
> With Guacamole Client, I'm getting the following sequence, which clearly
> show that we are using websocket (last line).
> "GET /guacamole/ HTTP/1.1" 304 -
> "GET /guacamole/app.css?v=0.9.9 HTTP/1.1" 200 44382
> "GET /guacamole/app.js?v=0.9.9 HTTP/1.1" 200 656348
> "GET
> /guacamole/api/languages?token=3215a5e3e4c4106cefd6bc6bd47e6d
> 7d09171136ba3c9e93d8ca6d8
> HTTP/1.1" 200 115
> "GET /guacamole/translations/en.json HTTP/1.1" 200 33115
> "POST /guacamole/api/tokens HTTP/1.1" 200 168
> "DELETE
> /guacamole/api/tokens/3215a5e3e4c4106cefd6bc6bd47e6d
> 7d09171136ba3c9e93d8ca6d8
> HTTP/1.1" 404 74
> "GET
> /guacamole/api/data/default/connectionGroups/ROOT/tree?token=
> bc03bd7a4ff3499c7e72247795cb54b7c485c27b0e9fc34805157fe
> HTTP/1.1" 200 266
> "POST /guacamole/api/tokens HTTP/1.1" 200 168
> "GET
> /guacamole/api/data/default/connections/xxxxxxxx?token=
> bc03bd7a4ff3499c7e72247795cb54b7c485c27b0e9fc34805157fe
> HTTP/1.1" 200 147
> "HEAD /guacamole/app/element/templates/blank.html HTTP/1.1" 200 -
> "HEAD /guacamole/app/element/templates/blank.html HTTP/1.1" 200 -
> "GET
> /guacamole/api/data/default/users/xxxxxxxx/permissions?token=
> bc03bd7a4ff3499c7e72247795cb54b7c485c27b0e9fc34805157fe
> HTTP/1.1" 200 188
> "GET
> /guacamole/websocket-tunnel?token=bc03bd7a4ff3499c7e72247795cb54
> b7c485c27b0e9fc34805157fe&GUAC_DATA_SOURCE=default&GUAC_
> ID=xxxxxxxx&GUAC_TYPE=c&GUAC_WIDTH=1238&GUAC_HEIGHT=800&
> GUAC_DPI=114&GUAC_IMAGE=image%2Fjpeg&GUAC_IMAGE=image%2Fpng
> HTTP/1.1" 101 -
>
>
>
>
> --
> View this message in context: http://apache-guacamole-
> incubating-users.2363388.n4.nabble.com/WebSockets-
> enablement-issue-SSL-Scanning-issue-tp524p625.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive
> at Nabble.com.
>

Mime
View raw message