Re: relayd l7 loadbalancing

2017-08-16 Thread Mischa Peters
> On 16 Aug 2017, at 10:41, Claudio Jeker wrote: > On Wed, Aug 16, 2017 at 10:27:58AM +0200, Maxim Bourmistrov wrote: >> >> Once connection is established, state is created in PF. Subsequent requests >> will be ???pipelined???. >> It is possible to influence this

Re: relayd l7 loadbalancing

2017-08-16 Thread Claudio Jeker
On Wed, Aug 16, 2017 at 10:27:58AM +0200, Maxim Bourmistrov wrote: > > Once connection is established, state is created in PF. Subsequent requests > will be ???pipelined???. > It is possible to influence this behavior by manipulating tcp.established in > pf.conf, > but I don???t think this is

Re: relayd l7 loadbalancing

2017-08-16 Thread Maxim Bourmistrov
Once connection is established, state is created in PF. Subsequent requests will be ’pipelined’. It is possible to influence this behavior by manipulating tcp.established in pf.conf, but I don’t think this is what you want. > 16 aug. 2017 kl. 10:05 skrev Mischa Peters : > >

relayd l7 loadbalancing

2017-08-16 Thread Mischa Peters
Hi All, I have somewhat the following config for relayd running on 6.1. And I am trying to forward certain request paths to different hosts. table { xx.xx.xx.131 } table { xx.xx.xx.31 } http protocol httpsfilter { match request header remove "Proxy" match request header append