On Tuesday, December 3, 2019, 1:19:48 AM GMT+1, Nick Couchman <[email protected]> wrote: > > Adding support for HTTP(S) might be doable, however it isn't as > straight-forward as it seems. It would involve considerable work on the > guacd side to attempt to render the web pages and then send images of those > pages across.
I understand this must be very complex. > The alternative to doing that rendering in guacd is just to have the > Guacamole system tunnel the HTTP(S) connection over the HTTP(S) > connection used for the other Guacamole traffic. However, if you're going to > do this, why not just use one of the existing reverse proxy > configurations out there? Guacamole can certainly be part of such a solution > to handle the remote desktop protocols, but you'll need to > find something else to do the HTTP(S) tunneling. Sure, I could use Squid as a reverse proxy. However, it would be "neat" to force users to log into the Guacamole portal so that they can see their usual services as icons (ssh, telnet, vnc, rdp) but also some internal HTTP(S) services. These HTTP(S) services could be full-fledged reverse proxies (eg. Squid) that forward to internal peers. So, not being an expert in HTTP proxying, could Guacamole "simply tunnel" HTTP requests/replies to and from clients and whatever reverse proxies are in the private network? Or would it only allow a redirection (or, simply put, an href link that would require opening firewalled ports or hosts)? Thanks, Vieri --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
