Sorry, I should have been more clear. Websockets is not being used to
proxy connections
mod_proxy_ws_tunnel is enabled and the websocket proxy is explicitly
declared in the apache configuration file as seen below.
<VirtualHost _default_:443>
ServerAdmin []
ServerName []
DocumentRoot /var/lib/tomcat8/webapps
ProxyPreserveHost On
<Location />
Order allow,deny
Allow from all
ProxyPass http://localhost:8080/guacamole/ flushpackets=on
ProxyPassReverse http://localhost:8080/guacamole/
</Location>
<Location /guacamole/websocket-tunnel>
Order allow,deny
Allow from all
ProxyPass ws://localhost:8080/guacamole/websocket-tunnel
ProxyPassReverse ws://localhost:8080/guacamole/websocket-tunnel
</Location>
Erik Berndt / Systems Administrator
5551 Wellington Rd, Gainesville, VA 20155
703.631.0004 x520 (Phone) / 703.257.1725 (Fax)
http://www.superiorpaving.net
Need to open an IT support ticket?
http://FixIT.superiorpaving.net/portal or [email protected]
On Wed, Jun 14, 2017 at 12:14 PM, Mike Jumper <[email protected]> wrote:
> On Wed, Jun 14, 2017 at 9:10 AM, Erik Berndt <[email protected]>
> wrote:
>>
>> I'm seeing the same issue using Apache with mod_proxy enabled, so I'm
>> watching this thread with curiosity.
>
>
> If you're referring specifically to the issue that websocket is not used,
> can you confirm whether your mod_proxy has websocket support?
>
> When proxying with Apache, the websocket tunnel must be explicitly declared
> in the configuration, or Apache will only ever use HTTP (even when
> JavaScript is trying to use websocket), and attempts to use websocket will
> fail:
>
> http://guacamole.incubator.apache.org/doc/gug/proxying-guacamole.html#websocket-and-apache
>
