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
ProxyPa
Hello Eric,
> Am 15.04.2015 um 19:47 schrieb Eric Covener :
>
> On Wed, Apr 15, 2015 at 12:18 PM, Marc Hörsken wrote:
>> Hello Eric,
>>
>>> Am 15.04.2015 um 14:05 schrieb Eric Covener :
>>>
>>> On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken wrote:
I was unable to find any useful resources
On Wed, Apr 15, 2015 at 12:18 PM, Marc Hörsken wrote:
> Hello Eric,
>
>> Am 15.04.2015 um 14:05 schrieb Eric Covener :
>>
>> On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken wrote:
>>> I was unable to find any useful resources about how to do this, yet.
>>> Can you point me in the right direction?
>
Hello Eric,
> Am 15.04.2015 um 14:05 schrieb Eric Covener :
>
> On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken wrote:
>> I was unable to find any useful resources about how to do this, yet.
>> Can you point me in the right direction?
>>
>> Is there some special header that needs to be sent by th
On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken wrote:
> I was unable to find any useful resources about how to do this, yet.
> Can you point me in the right direction?
>
> Is there some special header that needs to be sent by the server?
I would have thought this is purely a browser bug and the a
Hello Yann,
> Am 15.04.2015 um 12:32 schrieb Yann Ylavic :
>
> Once the connection is upgraded, mod_proxy_wstunnel (as its name
> suggests) creates a tunnel between the browser and the application.
> It will not check requests boundaries anymore, this is not HTTP but
> application data now, …
th
Hello Marc,
On Wed, Apr 15, 2015 at 10:50 AM, Marc Hörsken wrote:
>
> Now once a browser has upgraded a connection from HTTP to WebSocket traffic,
> all traffic is proxied to the WebSocket-server at 127.0.0.1:9001. The
> problem is that the browser continues to use that upgraded
> WebSocket-conne
Hello everyone,
I am experiencing weird connection issues with mod_proxy_wstunnel. My Apache 2
web server is still running on Debian Wheezy, so I had to backport
mod_proxy_wstunnel using the following patches:
https://github.com/mback2k/build-apache2.2-wstunnel
I compiled all mod_proxy* modules
