[
https://issues.apache.org/jira/browse/GUACAMOLE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091499#comment-17091499
]
Nick Couchman commented on GUACAMOLE-146:
-----------------------------------------
No, this was resolved in the follow-up pull request:
https://github.com/apache/guacamole-client/pull/394
> 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: 1.1.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
(v8.3.4#803005)
