guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GUACAMOLE-320) guacd-hostname property does not have intended effect
Date Thu, 08 Jun 2017 22:32:18 GMT

     [ https://issues.apache.org/jira/browse/GUACAMOLE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Jumper updated GUACAMOLE-320:
-------------------------------------
    Summary: guacd-hostname property does not have intended effect  (was: No connection from
guacamole webapps to guacd (separeted server scenario))

> guacd-hostname property does not have intended effect
> -----------------------------------------------------
>
>                 Key: GUACAMOLE-320
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-320
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole, guacamole-ext
>    Affects Versions: 0.9.13-incubating
>            Reporter: Karl Fiabeschi
>            Priority: Blocker
>
> If a value is specified for the {{guacd-hostname}} property in {{guacamole.properties}},
the value is effectively ignored, and an empty string is used for the hostname instead:
> {code:none}
> [http-bio-8080-exec-9] DEBUG o.a.g.net.InetGuacamoleSocket - Connecting to guacd at :4822.
> {code}
> If the guacd hostname is overridden through specifying a value for the {{proxy_hostname}}
column in the {{guacamole_connection}} table, things work as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message