Re: [FBR] proxies: adding rewritecond to reverseproxy for ws if remotepath exists

Thanks for the +1s. Pushed to ansible repo and has been run on proxies-stg. Tim On Fri, 22 Mar 2019 14:04:37 -0600 Tim Flink wrote: > I was hitting an issue where there were multiple reverseproxy > instances configured for a single host and some of the rewrite rules > were changing the request

Re: [FBR] proxies: adding rewritecond to reverseproxy for ws if remotepath exists

On 3/22/19 1:04 PM, Tim Flink wrote: > I was hitting an issue where there were multiple reverseproxy instances > configured for a single host and some of the rewrite rules were changing > the request when they shouldn't be. > > This patch adds a rewritecond to the websocket rewrite rule to make >

Re: [FBR] proxies: adding rewritecond to reverseproxy for ws if remotepath exists

Reviewed. +1 On Fri, 22 Mar 2019 at 16:04, Tim Flink wrote: > > I was hitting an issue where there were multiple reverseproxy instances > configured for a single host and some of the rewrite rules were changing > the request when they shouldn't be. > > This patch adds a rewritecond to the websock

[FBR] proxies: adding rewritecond to reverseproxy for ws if remotepath exists

I was hitting an issue where there were multiple reverseproxy instances configured for a single host and some of the rewrite rules were changing the request when they shouldn't be. This patch adds a rewritecond to the websocket rewrite rule to make sure that the REQUEST_URI starts with $remotepath