On Sun, Dec 24, 2017 at 4:40 AM, Jonathan Hunter <jmhunt...@gmail.com> wrote:
> Hi All, > > Just to follow up on this and for the benefit of others having the same > issue, I have now successfully worked around the problem. > > Printing does not work (for me, at least) when using guacamole via an > Apache reverse proxy *in HTTP mode*. I am not sure if this counts as a bug > - since everything else i.e. normal interactive use of guacamole > RDP/VNC/SSH/etc. sessions work fine in this configuration - but here are > the two steps I took to resolve: > > - Install Apache's mod_proxy_wstunnel (on Debian this is 'sudo a2enmod > proxy_wstunnel') > - Add a line in Apache's config to websocket-proxy the relevant URL. Note > that this line must come *before* the config entry that proxies the rest of > guacamole, since Apache's ProxyPass command operates on a first match wins > basis. > > (I did look at Chapter 4 of the documentation, and in particular the > 'Proxying with websocket' section, but I found I did not need the > ProxyPassReverse statement shown there; nor did I need to place it within a > <Location> section, in my config at least.) > > My Apache config now looks like this: > > ProxyPass /remoteaccess/websocket-tunnel > ws://docker.host:5678/guacamole/websocket-tunnel > > ProxyPass /remoteaccess/ > http://docker.host:5678/guacamole/ > > and printing now works perfectly. > > Mike/team - is this a bug? (Printing works via websocket but not via http) > and if so, is there a bug tracker I should report this to? Happy to do some > more digging/testing, if this isn't reproducible elsewhere. > I don't believe so, but it is noteworthy, and may require additional measures to work around this behavior. I suspect this may be due to browser-side limitations in the maximum number of concurrent HTTP requests to any one domain. - Mike
