request to the appropriate application server.
Based on the valuable inputs, it seems that the ws request url is
incomplete.
On Fri, May 12, 2017 at 6:46 PM, Eric Covener wrote:
> On Fri, May 12, 2017 at 9:10 AM, Vinod Mulani wrote:
> > Would there be any workaround to accomplish thi
I see, let me try and trace the requested websocket url in case of the
balancer.
Would there be any workaround to accomplish this type of task ? Would be
good to know.
VM
On Fri, May 12, 2017 at 6:26 PM, Eric Covener wrote:
> On Fri, May 12, 2017 at 8:51 AM, Vinod Mulani wrote:
>
Eric,
I would think so, since the direct request listed below goes well and the
ws url (i think) would be incomplete without it.
*ProxyPassMatch "^/(.*\websocket)$" "ws://10.x.x.x:80/$1"*
*VM*
On Fri, May 12, 2017 at 6:17 PM, Eric Covener wrote:
> On Fri, May 12,
I would love some inputs on the attempted configuration for load balancing
websocket & http requests in conjunction with ProxyPassMatch.
I am trying to load balance via Apache 2.4.25 two instances of an
application which intrinsically uses nginx as its internal proxy. It seems
straightforward to u
