You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Nick Couchman (JIRA)" <ji...@apache.org> on 2018/09/30 21:12:00 UTC
[jira] [Updated] (GUACAMOLE-146) Finer control of the tomcat
context path in Docker
[ https://issues.apache.org/jira/browse/GUACAMOLE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Couchman updated GUACAMOLE-146:
------------------------------------
Fix Version/s: (was: 1.0.1)
2.0.0
> Finer control of the tomcat context path in Docker
> --------------------------------------------------
>
> Key: GUACAMOLE-146
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-146
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
> Reporter: Emmanuel Frecon
> Assignee: Nick Couchman
> Priority: Minor
> Fix For: 2.0.0
>
>
> The current auto-deployment of the guacamole within tomcat leads to having the regular tomcat startup page mapped on {{/}} and guacamole mapped to {{/guacamole}}. Being able to control where guacamole gets to be deployed and served by tomcat would provide an increased flexibility when guacamole is fitted to existing architectures. For example, most docker-based deployments will use reverse-proxying to provide scalability and security.
> An initial fix for this is [available|https://github.com/apache/incubator-guacamole-client/pull/97/commits/1386239d3c12987daa774ed387a41c1471444f87]. However, this does not provide full flexibility. As [described|https://github.com/apache/incubator-guacamole-client/pull/97#issuecomment-268341268], using an environment variable to control the context path would be a much better solution as it would provide full flexibility while still maintaining backwards compabitibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)