[
https://issues.apache.org/jira/browse/GUACAMOLE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311434#comment-16311434
]
Nick Couchman commented on GUACAMOLE-57:
----------------------------------------
{quote}
For those "satellite spoke sites", having the ability to directly tunnel
HTTP(S) between guac-client and the final target thru guacd (or some other
daemon) would provide one tool giving to ops one interface showing one remote
systems tree and let them reach the equipment without having to deploy a
bouncer in every spoke or to deploy another application like reverse proxies
and siblings.
{quote}
So, I definitely understand your situation and your desire to have a single
solution that provides HTTP(S)/WS(S) for all of the protocols in a single
solution. I think the Guacamole protocol can help you out here, and can be a
part of a unified solution that would provide that for you - it's just my
opinion that putting the HTTP(S) traffic inside of Guacamole is not the right
way to go, as that's not what Guacamole is designed to do.
{quote}
Now, to be honest, we have a plan for ditching guacamole. I don't like it but
we have operational constraints.
{quote}
Sorry to hear this - I really do think that Guacamole would be a great solution
for you in this situation for the remote display protocol part of your
challenge. The HTTP(S) traffic could be easily handled by something like nginx
- you can parameterize the proxy_pass argument, for example, to get a dynamic
reverse proxy. See this page for more on that:
https://serverfault.com/questions/411832/dynamic-proxy-with-nginx-based-on-url-param
Also, I'll point out that I'm providing my opinion and input on putting HTTP(S)
traffic into Guacamole, but I'm no dictator and mine is not the final word on
this. Mike has provided some input related to this on GUACAMOLE-452, which
indicates which way he's leaning on the issue, but he hasn't indicated
definitively about this, nor have any of the other developers weighed in.
There are opinions beyond mine that matter :-).
And, while my opinion regarding this issue as it relates to the Guacamole
Server, Guacamole Client, and Guacamole protocol components is that it is "out
of scope," I do think that there's a potential here, outside of this project,
to create some sort of appliance that unifies Guacamole remote display access,
a web gateway (dynamic reverse proxy) of some sort, and maybe something else
like managed file transfer, into a single solution. I think this is what
you're looking for, and I think there's a market for it, even if there isn't a
current project or product with this implemented.
> New connection type "HTTP/HTTPS"
> --------------------------------
>
> Key: GUACAMOLE-57
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-57
> Project: Guacamole
> Issue Type: Improvement
> Reporter: Erik Pope
> Priority: Trivial
>
> I would love to see a new connection type "HTTP/HTTPS" Kind of like a web
> proxy.
> I use this tool for remote administration. Being able to access local only
> Admin Web pages would make this very useful.
> Some firewalls have web only management, Intranets, Local web apps, could all
> be accessed through this tool.
> I think this would be a killer addition.
> By the way this is an amazing program thanks for all the hard work on this
> project.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
