[ 
https://issues.apache.org/jira/browse/GUACAMOLE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638674#comment-16638674
 ] 

Felix Wolfheimer edited comment on GUACAMOLE-640 at 10/4/18 6:39 PM:
---------------------------------------------------------------------

Hi [~mike.jumper], good catch! Indeed, the nginx config on the system hosting 
Guacamole had a "X-Frame-Options DENY" line. I'm puzzled why this blocks 
guacamole though as this should only prevent embedding into other websites, if 
I understand the option correctly. Setting this to "SAMEORIGIN" solves the 
problem though and it works correctly now in Chrome 69. Maybe that's a bug in 
Chrome then?


was (Author: felix-wolfheimer):
Hi [~mike.jumper], good catch! Indeed, the nginx config on the system hosting 
Guacamole had a "X-Frame-Options DENY" line. I'm puzzled why this block 
guacamole though as this should only prevent embedding into other websites, if 
I understand the option correctly. Setting this to "SAMEORIGIN" solves the 
problem though and it works correctly now in Chrome 69. Maybe that's a bug in 
Chrome then?

> Guacamole doesn't work in Chrome 69
> -----------------------------------
>
>                 Key: GUACAMOLE-640
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-640
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole, guacamole-client
>    Affects Versions: 0.9.14
>            Reporter: Felix Wolfheimer
>            Priority: Major
>         Attachments: image-2018-10-04-17-27-26-450.png, 
> image-2018-10-04-17-30-02-466.png
>
>
> In the most recent update of Google Chrome, the guacamole client doesn't work 
> anymore. The behavior is as follows:
> Login works fine. Then, a blank page is shown with a connection error message:
> !image-2018-10-04-17-27-26-450.png!
> In the Chrome development tools one can see the following errors:
> !image-2018-10-04-17-30-02-466.png!
> If I connect to this same instance using either Chrome 68, Firefox 62, or 
> Internet Explorer, everything works fine.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to