Re: SSL RDP Download file fails

2018-01-08 Thread Mike Jumper
Regarding the non-WebSocket messages:

On Mon, Jan 8, 2018 at 1:03 PM, Adrian Owen  wrote:
> Hi Mike,
>
> Yes Chrome shows this error:
>
> The key "target-densitydpi" is not supported.
>

This is a warning regarding a legacy meta key used to hint to older
browsers that Guacamole is a web application designed to work at the
device's native DPI. It continues to exist for the benefit of older
browsers. For newer browsers which do not support this meta key,
Guacamole does not depend on it.

> angular.js:11699 TypeError: Cannot read property 'guac-full-name' of
> undefined
> at app.js?v=0.9.13-incubating:293
> at angular.js:9442
> at angular.js:13292
> at m.$eval (angular.js:14547)
> at m.$digest (angular.js:14363)
> at m.$apply (angular.js:14652)
> at l (angular.js:9734)
> at P (angular.js:9924)
> at XMLHttpRequest.H.onload (angular.js:9865)
> (anonymous) @ angular.js:11699
>

I have opened an issue in JIRA for this. It is a regression due to the
recently-added support for user profile attributes. Thankfully, the
error occurs at a point where it has no impact on Guacamole's
functionality. It is unrelated to the issue at hand:

https://issues.apache.org/jira/browse/GUACAMOLE-480

- Mike


RE: SSL RDP Download file fails

2018-01-08 Thread Adrian Owen
I'll try that and feedback,

Cheers, Adrian

-Original Message-
From: Mike Jumper [mailto:mike.jum...@guac-dev.org] 
Sent: 08 January 2018 21:15
To: user@guacamole.apache.org
Subject: Re: SSL RDP Download file fails

Under the assumption that Tomcat has issues with it's HTTPS connector vs. 
WebSocket, I'd recommend switching things over to using a reverse proxy like 
Apache or Nginx for SSL termination. If the problem is the same as the issue 
referenced in the mailing list thread I mentioned earlier, that should resolve 
this.

Though Tomcat provides some documentation on WebSocket-related configuration 
[1], and it does mention SSL, just using a proxy for SSL termination may be the 
easiest solution here:

http://guacamole.apache.org/doc/gug/proxying-guacamole.html

- Mike

[1] https://tomcat.apache.org/tomcat-8.0-doc/web-socket-howto.html


On Mon, Jan 8, 2018 at 1:03 PM, Adrian Owen  wrote:
> Hi Mike,
>
>
>
> Yes Chrome shows this error:
>
>
>
> The key "target-densitydpi" is not supported.
>
> angular.js:11699 TypeError: Cannot read property 'guac-full-name' of 
> undefined
>
> at app.js?v=0.9.13-incubating:293
>
> at angular.js:9442
>
> at angular.js:13292
>
> at m.$eval (angular.js:14547)
>
> at m.$digest (angular.js:14363)
>
> at m.$apply (angular.js:14652)
>
> at l (angular.js:9734)
>
> at P (angular.js:9924)
>
> at XMLHttpRequest.H.onload (angular.js:9865)
>
> (anonymous) @ angular.js:11699
>
> app.js?v=0.9.13-incubating:129 WebSocket connection to 
> 'wss://192.168.242.88:9943/guacamole/websocket-tunnel?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F_DATA_SOURCE=json_ID=RDP%20wensan%40SERLOCDEV12%20localadmin%40SERHUBSMTP01%20SERHUBSMTP01_TYPE=c_WIDTH=800_HEIGHT=600_DPI=96_AUDIO=audio%2FL8_AUDIO=audio%2FL16_IMAGE=image%2Fjpeg_IMAGE=image%2Fpng_IMAGE=image%2Fwebp'
> failed: Error during WebSocket handshake: Unexpected response code: 
> 404
>
> connect @ app.js?v=0.9.13-incubating:129
>
> :9943/guacamole/api/session/tunnels/1c5b44cb-1a56-45c4-9890-737f7be708
> bd/activeConnection/connection/sharingProfiles?token=5A4E4579D23784236
> 04D5D90DF3CA7302AC998063E095D41768D428762B8E09F
> Failed to load resource: the server responded with a status of 404 
> (Not
> Found)
>
>
>
> Adrian
>
>
>
> From: Mike Jumper [mailto:mike.jum...@guac-dev.org]
> Sent: 08 January 2018 20:47
> To: user@guacamole.apache.org
> Subject: Re: SSL RDP Download file fails
>
>
>
> On Mon, Jan 8, 2018 at 12:44 PM, Mike Jumper 
> 
> wrote:
>
> Do you see anything in the network tab of your browser's dev tools 
> when the upload fails? If Tomcat is rejecting the request, the 
> response within the network tab may reveal the cause. Depending on 
> whether IE successfully logs such things, you may need to switch to a 
> different browser to obtain the necessary information.
>
>
>
>
>
> It might also be interesting to check whether WebSocket is failing 
> when Tomcat is configured for HTTPS. There was another thread on this 
> list recently which dealt with printing not working if the HTTP tunnel 
> was in use. As file transfer goes over the same underlying mechanism 
> as printing, this could cause what you're seeing.
>
>
>
> https://lists.apache.org/thread.html/ae6a8a0c8bfe1a5a84aad779a3b594855
> e408f78ce20dc6f1b5da4ad@%3Cuser.guacamole.apache.org%3E
>
>
>
> - Mike
>
>


Re: SSL RDP Download file fails

2018-01-08 Thread Mike Jumper
Under the assumption that Tomcat has issues with it's HTTPS connector
vs. WebSocket, I'd recommend switching things over to using a reverse
proxy like Apache or Nginx for SSL termination. If the problem is the
same as the issue referenced in the mailing list thread I mentioned
earlier, that should resolve this.

Though Tomcat provides some documentation on WebSocket-related
configuration [1], and it does mention SSL, just using a proxy for SSL
termination may be the easiest solution here:

http://guacamole.apache.org/doc/gug/proxying-guacamole.html

- Mike

[1] https://tomcat.apache.org/tomcat-8.0-doc/web-socket-howto.html


On Mon, Jan 8, 2018 at 1:03 PM, Adrian Owen  wrote:
> Hi Mike,
>
>
>
> Yes Chrome shows this error:
>
>
>
> The key "target-densitydpi" is not supported.
>
> angular.js:11699 TypeError: Cannot read property 'guac-full-name' of
> undefined
>
> at app.js?v=0.9.13-incubating:293
>
> at angular.js:9442
>
> at angular.js:13292
>
> at m.$eval (angular.js:14547)
>
> at m.$digest (angular.js:14363)
>
> at m.$apply (angular.js:14652)
>
> at l (angular.js:9734)
>
> at P (angular.js:9924)
>
> at XMLHttpRequest.H.onload (angular.js:9865)
>
> (anonymous) @ angular.js:11699
>
> app.js?v=0.9.13-incubating:129 WebSocket connection to
> 'wss://192.168.242.88:9943/guacamole/websocket-tunnel?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F_DATA_SOURCE=json_ID=RDP%20wensan%40SERLOCDEV12%20localadmin%40SERHUBSMTP01%20SERHUBSMTP01_TYPE=c_WIDTH=800_HEIGHT=600_DPI=96_AUDIO=audio%2FL8_AUDIO=audio%2FL16_IMAGE=image%2Fjpeg_IMAGE=image%2Fpng_IMAGE=image%2Fwebp'
> failed: Error during WebSocket handshake: Unexpected response code: 404
>
> connect @ app.js?v=0.9.13-incubating:129
>
> :9943/guacamole/api/session/tunnels/1c5b44cb-1a56-45c4-9890-737f7be708bd/activeConnection/connection/sharingProfiles?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F
> Failed to load resource: the server responded with a status of 404 (Not
> Found)
>
>
>
> Adrian
>
>
>
> From: Mike Jumper [mailto:mike.jum...@guac-dev.org]
> Sent: 08 January 2018 20:47
> To: user@guacamole.apache.org
> Subject: Re: SSL RDP Download file fails
>
>
>
> On Mon, Jan 8, 2018 at 12:44 PM, Mike Jumper 
> wrote:
>
> Do you see anything in the network tab of your browser's dev tools when the
> upload fails? If Tomcat is rejecting the request, the response within the
> network tab may reveal the cause. Depending on whether IE successfully logs
> such things, you may need to switch to a different browser to obtain the
> necessary information.
>
>
>
>
>
> It might also be interesting to check whether WebSocket is failing when
> Tomcat is configured for HTTPS. There was another thread on this list
> recently which dealt with printing not working if the HTTP tunnel was in
> use. As file transfer goes over the same underlying mechanism as printing,
> this could cause what you're seeing.
>
>
>
> https://lists.apache.org/thread.html/ae6a8a0c8bfe1a5a84aad779a3b594855e408f78ce20dc6f1b5da4ad@%3Cuser.guacamole.apache.org%3E
>
>
>
> - Mike
>
>


RE: SSL RDP Download file fails

2018-01-08 Thread Adrian Owen
Hi Mike,

Yes Chrome shows this error:

The key "target-densitydpi" is not supported.
angular.js:11699 TypeError: Cannot read property 'guac-full-name' of undefined
at app.js?v=0.9.13-incubating:293
at angular.js:9442
at angular.js:13292
at m.$eval (angular.js:14547)
at m.$digest (angular.js:14363)
at m.$apply (angular.js:14652)
at l (angular.js:9734)
at P (angular.js:9924)
at XMLHttpRequest.H.onload (angular.js:9865)
(anonymous) @ angular.js:11699
app.js?v=0.9.13-incubating:129 WebSocket connection to 
'wss://192.168.242.88:9943/guacamole/websocket-tunnel?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F_DATA_SOURCE=json_ID=RDP%20wensan%40SERLOCDEV12%20localadmin%40SERHUBSMTP01%20SERHUBSMTP01_TYPE=c_WIDTH=800_HEIGHT=600_DPI=96_AUDIO=audio%2FL8_AUDIO=audio%2FL16_IMAGE=image%2Fjpeg_IMAGE=image%2Fpng_IMAGE=image%2Fwebp'
 failed: Error during WebSocket handshake: Unexpected response code: 404
connect @ app.js?v=0.9.13-incubating:129
:9943/guacamole/api/session/tunnels/1c5b44cb-1a56-45c4-9890-737f7be708bd/activeConnection/connection/sharingProfiles?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F
 Failed to load resource: the server responded with a status of 404 (Not Found)

Adrian

From: Mike Jumper [mailto:mike.jum...@guac-dev.org]
Sent: 08 January 2018 20:47
To: user@guacamole.apache.org
Subject: Re: SSL RDP Download file fails

On Mon, Jan 8, 2018 at 12:44 PM, Mike Jumper 
> wrote:
Do you see anything in the network tab of your browser's dev tools when the 
upload fails? If Tomcat is rejecting the request, the response within the 
network tab may reveal the cause. Depending on whether IE successfully logs 
such things, you may need to switch to a different browser to obtain the 
necessary information.


It might also be interesting to check whether WebSocket is failing when Tomcat 
is configured for HTTPS. There was another thread on this list recently which 
dealt with printing not working if the HTTP tunnel was in use. As file transfer 
goes over the same underlying mechanism as printing, this could cause what 
you're seeing.

https://lists.apache.org/thread.html/ae6a8a0c8bfe1a5a84aad779a3b594855e408f78ce20dc6f1b5da4ad@%3Cuser.guacamole.apache.org%3E

- Mike



Re: Printing using docker image?

2018-01-08 Thread Mike Jumper
On Wed, Jan 3, 2018 at 12:35 PM, Jonathan Hunter 
wrote:

>
>
> On 1 January 2018 at 21:01, Mike Jumper  wrote:
>
>> On Sun, Dec 24, 2017 at 4:40 AM, Jonathan Hunter 
>> wrote:
>>
>>> Mike/team - is this a bug? (Printing works via websocket but not via
>>> http) and if so, is there a bug tracker I should report this to? Happy to
>>> do some more digging/testing, if this isn't reproducible elsewhere.
>>>
>>
>> I don't believe so, but it is noteworthy, and may require additional
>> measures to work around this behavior. I suspect this may be due to
>> browser-side limitations in the maximum number of concurrent HTTP requests
>> to any one domain.
>>
>
> Is there a bug / feature tracker that I should add this to? Happy to log
> if that would help.
>
>
Yep. We use JIRA as our issue tracker:

https://issues.apache.org/jira/browse/GUACAMOLE/

- Mike


Re: SSL RDP Download file fails

2018-01-08 Thread Mike Jumper
On Mon, Jan 8, 2018 at 12:44 PM, Mike Jumper 
wrote:

> Do you see anything in the network tab of your browser's dev tools when
> the upload fails? If Tomcat is rejecting the request, the response within
> the network tab may reveal the cause. Depending on whether IE successfully
> logs such things, you may need to switch to a different browser to obtain
> the necessary information.
>
>
It might also be interesting to check whether WebSocket is failing when
Tomcat is configured for HTTPS. There was another thread on this list
recently which dealt with printing not working if the HTTP tunnel was in
use. As file transfer goes over the same underlying mechanism as printing,
this could cause what you're seeing.

https://lists.apache.org/thread.html/ae6a8a0c8bfe1a5a84aad779a3b594855e408f78ce20dc6f1b5da4ad@%3Cuser.guacamole.apache.org%3E

- Mike


Implement support for in-browser playback of screen recordings

2018-01-08 Thread Amarjeet Singh
Hi Team,


If  " Implement support for in-browser playback of screen recordings"  is
fixed in 0.9.13 version then How can I play screen recordings from the
Browser itself ?



Thanks and Regards,
Amarjeet Singh