necouchman commented on a change in pull request #95:
URL: https://github.com/apache/guacamole-website/pull/95#discussion_r750790823
##########
File path: faq.md
##########
@@ -262,6 +262,15 @@ method for X11, which is too complex. This is not
necessary, though - as far as
performance is concerned, there is an X.Org driver for Guacamole currently
under development which achieves the same goal (see above).
+### I would like to access web pages via Guacamole. Can you add support for
HTTP(s)? {#support-http}
+No. Guacamole is designed to be a remote desktop client, and the goal is not
+to provide a complete remote access solution (VPN, Proxy, Zero-Trust, etc.).
There
+are many existing services available for VPN, Reverse Proxy, and the like, and
Guacamole
+can complement these solutions by providing a remote desktop component to those
Review comment:
> Guacamole is designed and intended to be a complete remote access
solution, and is particularly well-suited to Zero-Trust and taking the place of
what would traditionally involve a VPN given its built-in access controls and
authn/authz layer.
Yes, that's a good point. I can broaden this a bit.
> Given how frequently this is requested and the fact that we support
RemoteApp, I occasionally wonder whether we may be wrong to exclude access to
webapps from the concept of remote access.
I'm definitely not opposed to changing our minds on this. I'm curious how
you'd foresee this operating within the Guacamole framework - that is, would
HTTP traffic be tunneled, somehow, within the Guacamole protocol, or would we
bypass the Guacamole protocol altogether? Would guacd still do the translation
and connection management between the tunnel and the back-end system?
Presumably we could leverage one of several possibly HTTP libraries for that,
but seems like a pretty extensive set of changes to make to support rendering
pages between guacd and the remote browser, unless we don't use the Guacamole
protocol at all and just act as a reverse proxy.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
