Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of info@marc-hoersken.de
 designates 89.238.84.48 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: =?utf-8?Q?Marc_H=C3=B6rsken?= <info@marc-hoersken.de>
In-Reply-To: <71CFE936-6937-4F45-BAD6-0AA39FB146E5@marc-hoersken.de>
Date: Fri, 17 Apr 2015 15:38:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB005100-7B3A-4902-9F12-968266BCAB23@marc-hoersken.de>
References: <A480E2DF-FA4A-40DE-BF74-20B50459A6D1@marc-hoersken.de>
 <CAKQ1sVOmAw4q=jYV9cWqjMTZB-MdadPNQY1phC+gOu9rb_5mXA@mail.gmail.com>
 <856DC4F6-CC40-442A-BB18-9BEA4A658459@marc-hoersken.de>
 <CALK=YjNnkEbR0E+Dmh+4ucc7L+S+PPLgp2qHp2gaau49KxfKyA@mail.gmail.com>
 <7BBB98BB-EF90-40A3-A428-FAA175EE9CDF@marc-hoersken.de>
 <CALK=YjPQfWeCN=a1-DB3L5zagQGTohwiw+YtxySzCYQ4+-e6NQ@mail.gmail.com>
 <71CFE936-6937-4F45-BAD6-0AA39FB146E5@marc-hoersken.de>
To: users@httpd.apache.org
Subject: Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

Hello everyone,

I just figured out the configuration issue causing my problem.

Original configuration mod_proxy_wstunnel with SwampDragon:

ProxyPass /data/ ws://127.0.0.1:9001/data/
ProxyPassReverse /data/ ws://127.0.0.1:9001/data/
ProxyPass /settings.js http://127.0.0.1:9001/settings.js
ProxyPassReverse /settings.js http://127.0.0.1:9001/settings.js
ProxyPreserveHost On
ProxyRequests Off
ProxyVia On

The following configuration for mod_proxy_wstunnel with SwampDragon =
works fine:

ProxyPassMatch /data/(\d+)/(\w+)/websocket =
ws://127.0.0.1:9001/data/$1/$2/websocket
ProxyPass /data/info http://127.0.0.1:9001/data/info
ProxyPassReverse /data/info http://127.0.0.1:9001/data/info
ProxyPass /settings.js http://127.0.0.1:9001/settings.js
ProxyPassReverse /settings.js http://127.0.0.1:9001/settings.js
ProxyPreserveHost On
ProxyRequests Off
ProxyVia On

The issue was caused by the fact that /data/info is requested before a =
WebSocket-upgrade request to /data/(\d+)/(\w+)/websocket is performed. =
Because /data/info was redirected to the WebSocket-server using the same =
rule as /data/(\d+)/(\w+)/websocket before, mod_proxy_wstunnel continued =
to also forward all HTTP-traffic to the WebSocket-server.

Hope this helps in case anyone else runs into the same problem. You have =
to make sure that ws:// or was:// forwarding is only configured for the =
actual WebSocket-URL and does not affect any other requests.

Thanks for pointing me into the right direction.

Best regards,
Marc=

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org